Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ASSIGN method
Message
From
27/09/1999 18:49:33
 
 
To
26/09/1999 05:05:11
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Title:
Miscellaneous
Thread ID:
00267357
Message ID:
00269699
Views:
29
Hi Walter ---

>I strongly suggest nevere to use these features *unless* there is no other way out.

ACCKKK! How can you say that? Sure, you have other ways of doing this via Let_ and Set_ equivalents but _ASSIGN allows for event firing on value changes without explicit calls. It also allows you to hide the implementation of property changes in COM objects.

I'll give you an example of day-to-day use. IF you have a FormState property in your Form class that tracks whether you are adding, modifying, or just looking at data, you can put all the enables, disables, and caption changes in one place: FormState_Assign.

>Personally I've got the opinion these features should be available because it attempts less talented programmers to write less constructive code. In the few cases i've found that these features *might* be of any help, it clearly pointed out that it was in fact a shortcoming in the VFP OO model (for e.g. missing events).

Actually, adding ACCESS and ASSIGN enhances the object model.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform