> 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. :-) That might not be too difficult because ... because I think that in the extensions library there is code which implements behaviours on both GNU and NeXT runtime. So you could read that code to learn how to do, and then fix the gnustep-base behaviours implementation to work with the NeXT runtime as well. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
