>>Hi,
>>
>>I have a function (fairly small) that loads a cursor from XML (application configuration values). This function can be in the main application .PRG or in some other MISC_FUNC.PRG (loaded in the main .PRG via SET PROCEDURE TO MISC_FUNC ADDITIVE). Does it matter for the speed of the program is this function in one place or the other? Any other things to consider as far as the place for this function?
>>TIA
>
>A single standalone .prg is my first choice - if it's a function that VFP should have. Compiled into the exe, there is no speed advantage to having the function inside another .prg. In fact, even having to execute the line SET PROCEDURE TO someproclib.prg takes time. If you might want the advantage of sub-classing, consider making it into a class.
Yes, putting the function in a separate PRG is what I ended up doing. I thought about putting this function into a the application class (as a method) but discarded this idea.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
