>>So you have a SEPARATE prg file for each Func/Proc?
>>
>>To me, there is some bene to have them all in one file, or at least grouping certain ones within perhaps a few different .prg files. It makes comparing and reviewing a little quicker since you can scroll up or down withing the file quickly, and Document View is some help also. You don't get that with separate files.
>
>
>OTOH, if you put everything in one big prg file, all of it goes into the app, needed or not. Also, if you want a version of a function/procedure to apply to one app but a different version to another, you either have to yank it out from the big prg, or start bracketing the versions somehow or resort to other tricks. If you break it into a few prg files (by, say, purpose, category or whatever), there will always be borderline cases which you will think belong into one on odd days, and into another on even ones... so half of the time you'll be looking for it in the wrong place.
>
>My recipe is simple: make them all methods of one big oSys class, so you can at least subclass it as needed, and keep it all in sys.prg, or do one function one prg.

Sounds very reasonable.