As you wrote elsewhere: JS has documented it. That makes a huge difference.
>Peter,
>
>you may have read me stating that vfp has some JS-like behaviours.
>This is the prototype similar way of doing things.
>.Init() is your friend for more class like behaviour.
>
>regards
>
>thomas
>
>>Well then, why is this not in the documentation?! It is very important to know this, isn't it. I can say I'm a really experienced vfp developer, doing vfp since 1990. But this has never been told or explained to me, nowhere, not in the docs, not in the Hackers guide. 'By-design' may be what has been told to you, but to me that sounds like a rationalisation, to hide the real reason: a design flaw or simply a blind spot for this when implementing it, in both cases a flaw they somehow didn't want to repair.
>>
>>Re-using the cached version of a previously instantiated object is smart enough, but of course that should not imply the re-use of any initial values.
>>
>>>FoxPro does neat things with caching classes you have referenced so it does not have to re-create them from
>>>scratch every time you use them.
>>>
>>>This is the same problem experienced in VCX-based classes where the property value is created with an '=',
>>>which is executed the first time the class is created only.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.