Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Variable scope
Message
From
17/08/1999 14:13:39
 
 
To
17/08/1999 14:06:42
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00254565
Message ID:
00254622
Views:
23
>Hi Ed,
>
>>The easiest way would be to make them properties of the form, rather than variables. The only memvars that would persist would be globals (PUBLICs) and there are all sorts of funky side effects, on top of being bad OOP in general. Form properties are visisble within the form, and have the necessary persistence and encapsulation you want.
>
>I've thought about this in the past, would it be agaisnt OO to create an oGlobalVars object that sits like an oApp, but you wouldn't want to bog oApp down with somewhat un-relavant variables? The property would create its self using an AddProperty in a this_assign. I realize this would not (or should not) be used alot. But from returning a value from a NewObject or something just plop that Var in oGVars.

If you're going to violate encapsulation, why bother with it?
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform