Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
#DEFINE - Why?
Message
From
31/03/2008 10:54:23
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01306848
Message ID:
01306947
Views:
11
>>Declared PRIVATE in the main program does allow it to be available throughout the app. Or make it a project level property on an object. You could even call it oProject.Constants.My_Constant if you wanted.
>
>This leads us to another interesting point. Variables and properties can be changed. The defined constants can only be re-defined using #UNDEF directive first.

Someone else said that too. It was the only point that I've seen so far that gave the DEFINE any real value to me, but I don't know if it's enough to use them instead of variables. If there are a couple hundred variables in your code, what's adding 20 more? I would rather have them all defined in the same place anyway.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform