Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Class Method in Report
Message
 
To
14/04/2008 01:16:55
Lutz Scheffler (Online)
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 8 SP1
Miscellaneous
Thread ID:
01309629
Message ID:
01310408
Views:
13
Agnes,

PRIVATE variables are visible to the routine that creates them and all routines below that one in the calling stack. PUBLIC variables live beyond the end of the routine that creates them, that is the ONLY thing that PUBLIC causes is for the variablke to live beyoind the end of the program that created it and it is very poor design to require that a variable live beyond the life of the rountine that created it. It violates every tenant of programming from structured to OOP. No program should have a left over impact on the environment from which it was called other than the purpose for its existance. All programs should clean up any memory they use before they exit and PUBLIC variables are a direct violation of this principle.

I have no problem condeming PUBLIC variables as they are the bane of all things good in program design.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform