I think I found a flaw in the _object>>_delegated message: it doesn't know the size of the new type, so it may answer an incorrect object if methods in the new family expect an object that is bigger than the old one (this prototypical object will always be the size of the original, though newer objects may still be created correctly).
To fix this, I'd suggest adding a size parameter to _object>>_delegated. Can anybody else verify this and/or provide a better fix? -- Michael FIG <[EMAIL PROTECTED]> //\ http://michael.fig.org/ \// _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
