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.



>>>1. No need to change PROCEDURE to FUNCTION. You can call either one as a function.
>>
>>Oh, I didn't really plan to change them; was just asking it theoritcally to prove the matter.
>
>Unlike most, I do not use a procedure library at all. That means I never have to say SET PROCEDURE TO nor worry about which one is open. A .prg like this...
>
>myudf.prg
>LPARAMETERS tn1, tc2
>*whatever
>*optional return
>
>can be called by DO myudf with params or MyUDF(params). Lots of typing savings excluding all those PROCEDURE and FUNCTION declarations ;)