Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Is it advisable to modify GenScrn to hardcode proc-func
Message
 
À
25/10/2005 18:31:02
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Versions des environnements
Visual FoxPro:
FoxPro Dos
Divers
Thread ID:
01061979
Message ID:
01062150
Vues:
13
Hi Dragan

>unless you go and waste a lot of time inserting #name directives everywhere.

I was hoping to modify GenScrn in such a manner that the insertion is done by it. In short found #NAME no change, not found #NAME generate a meaningless name and store in the snippet as #NAME xxxx.

>What you may want to do is to keep the generated code out of source control (as it's just output).

The generated code though is in the SCM is used to manually check for the changes (at SCX and SCT are binary) so when I find that by mistake I have Ctrl+W'd a screen file I can avoid including it and revert it.

>- do you really care about this issue?

Too an extent yes.

>- do you have the time to play with it?

Couple of hours if I can get the result by changing GenScrn, not the whole set of snippets.

But modifing GenScrn or not apart what would your advise be if I somehow got the #NAME directives into the screen files snippets with SYS() generated names will it have adverse effects?

Please advise.
Regards
Bhavbhuti
___________________________________________
Softwares for Indian Businesses at:
http://venussoftop.tripod.com
___________________________________________
venussoftop@gmail.com
___________________________________________
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform