>>With only some extra code they would have re-initialized the properties, without almost no impact on the performance. So, your idea that it's optimization is incorrect.
>
>Imagine initializing some Set(Path) like string of directories for the current running machine,
>testing out a couple of hundred possible settings - that could take significant time.
>>
>>Elsewhere you seem to suggest that it is not the case in scx's. If that's true (what I believe to be), then that's an extra argument against the idea that it's optimization, isn't it?!
>
>Have not looked at it, but might be a side effect of calling via Do Form -
>similar to the small differences of add object and .addobject()
>or acessability of pseudo classes before init() has run.
>See Drew Speedie stuff for in depth discussion of such things.

You get the pseudo class behavior even in VFP9, if you use memberclasses which have some code in their .init() (or maybe even if not) - they get initialized, but with the PEMS as in their class, not as in the instance, and their class init runs before any other objects on the parent object are instantiated, even those defined as members in the parent class. IOW, that even breaks the inside out order. Documented? I wouldn't say. But there it is.