Stephen Brandon wrote: > > ... > received module: GSCompatibility.m > gathering selectors from module: GSCompatibility.m > received module: PerformSound.m > gathering selectors from module: PerformSound.m > received module: SndConditionLock.m > Record selector NSEraseRect:[(null)] as: 1459 > Record selector NSHighlightRect:[(null)] as: 1460 > Record selector NSRectClip:[(null)] as: 1461 > Record selector NSRectClipList::[(null)] as: 1462 > Record selector NSRectFill:[(null)] as: 1463 > (etc) > > Needless to say, my SndConditionLock class makes absolutely > no reference to any of the graphics functions/selectors. > There are not even any headers imported that would refer to > appkit things. Looking at the order of output from > gnustep-objc-1.1.0/init.c, these selectors should definitely > be related to the preceding module name (as far as I can > make out). >
Well these lines would show up if you used these selectors in that module. If you haven't, and there is little reason to do so, that's very odd. I have to say I'm baffled by the whole thing. I've tried some things myself (on Win98) and got pretty much the same results (minus the spurious selectors), even thought it appears the gnustep-gui and gnustep-base are linked the same way. -- Adam Fedor, Digital Optics | I'm glad I hate spinach, because http://www.doc.com | if I didn't, I'd eat it, and you http://www.gnustep.org | know how I hate the stuff. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
