>>>>We had, well, let's just say, a questionable procedure name popup on a client's PC as part of an error message. We now need a way to find all the procedure/function names in our system and review them. Any reasonably easy way to do that?
>>>
>>>I still believe the prediliction for procedure and class libraries is a hold over from foxbase days. For me, all I do is
>>>
>>>DIR PRG\*.PRG to get a list of the procedures in my system.
>>>DIR VCX\*.VCX to get a list of the classlibs in my system.
>>
>>But it's the names of the procedures/functions I need to get from those files. I think I'm just going to use my Search and Replace from Funduc.
>
>From our previous conversations with Mike on the topic I believe he suggests using one function per program file, so in his case the name of the program will match the function name.
>
>I'm not sure he suggests to use the same approach for classes.

I do indeed. The only exception for me is a compound class. Note the scx structure is identical to the vcx. An scx is a compound class. It makes sense for them to exist as a package. The vcx containing a bunch of unrelated classes does not seem sensible to me.