Follow-up Comment #16, bug #25033 (project gnustep): Actually my suggestion is not so great after all. Merely haven NXConstantString categories would still break the class hierarchy.
I'm not sure how gnustep's constant strings worked with compilers prior to -fconstant-string-class. I.e. how we can unsure the runtime will always use our: NXConstantString : NSString : NSObject instead of libobjc's NXConstantString : Object Maybe we should try to "adjust" the runtime structures during +load of our NXConstantString class. I'm not sure exactly how to do that (especially efficiently [i.e. without iterating of all known classes to find both versions of NXConstantString for every GNUstep process]). Maybe someone else has a better suggestion, or know more about how/whether this worked with compilers prior to -fconstant-string-class. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?25033> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep