Am Freitag den, 22. M�rz 2002, um 14:36, schrieb Nicola Pero:
> >> The reason I came across such an issue is, on NeXT runtime >> behavior_class_add_class() makes major trouble. A possible >> conclusion might be, we have to get rid of behavior adding on >> NeXT runtime, at least in +initialize methods. > > An alternative conclusion would be that behaviours should be > fixed to work > on the NeXT runtime as well. :-) Before asking you to make major changes, I'll demonstrate you why it is unavoidable, of course. I don't think making changes to NeXT runtime itsself makes sense since changes commited to Darwin might take a year or longer until they show up in OS X. > That might not be too difficult because ... because I think that in the > extensions library Which lib are you exactly speaking of? Is it part of GNUstep base? Thanks, Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
