Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is it advisable to modify GenScrn to hardcode proc-func
Message
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Environment versions
Visual FoxPro:
FoxPro Dos
Miscellaneous
Thread ID:
01061979
Message ID:
01062085
Views:
9
This message has been marked as a message which has helped to the initial question of the thread.
>I recently had to make a copy of a FDP25 project. As the directory had changed the project did a recompile of all the screen files (especially), menu files. According to Source Control these became modified files. All that had really changed was the Date/Time at the top of the .SPR and the Procedure/Function names that were generated at the compile time.
>
>I feel this is a lot of unnecessary flagging of source codes.
>
>I was hoping to change the GenScrn.PRG as follows:
>- Not to change the date/time (if logically possible) or altogether not print the date/time` at all.
>- If a proc./func. name has to be generated, then the code snippet (memo) should be replaced with a #NAME directive containing the newly generated name. I can do that in GetCName() function or whereever the snippet is first encountered.
>
>Please advise of any pitfalls that you feel maybe lurking if I went ahead with it.

You may want to try using GenScrnX to do this, see http://www.stevenblack.com/SBCPublicDomain.asp. You have access to the SCX table before it goes to GenScrn.prg in that program, plus you can modify the SPR output there as well - all without changing GenScrn.prg. There are no comments in GenScrnX, but I've always maintained that it is a self-documenting FoxPro program. :)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform