Hello, I have several frameworks that I want to register their UTI using +initialize for each class but I have a problem that the parent class type may not already be +initialize'd and so I need to manually call [aClass class] to activate their +initialize's. This is a little inconvenience as it must know exactly what class was responsible for a needed supertype hence it will break the encapsulation of the framework that is responsible for the supertype registration. In the case that the supertype registrations can be guaranteed to be initialized at some states in the application, would it be convenience to allow some temporary supertype registration that would just raise exceptions by default but to be replaced by real registrations later? (I could also just add some per-frameworks global functions to encapsulate the initializations though) Thanks, Al.
_______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
