--- In [email protected], "Michael Schmalle" <[EMAIL PROTECTED]> wrote: > > Clarification; > > Children can be created at any time AFTER super(). > > Since we all design software with a design, any property committal in a > super() call has nothing to do with an instance of a child you create in the > subclass (this is bad design). Thus, the above logic holds true.
But someone subclassing your Class may not have the same understanding of your design that you do, and it is quite common for developers to try to set properties on child objects in commitProperties. I've even been advised to do so in this forum by people I respect. Maybe in retrospect it was a bad idea to take such advice, but new developers are going to continue getting such advice and taking it. So it very much matters where you create children when _other people_ are going to be subclassing your work. -Amy -Amy
