Saso, Citát Sašo Kiselkov <[EMAIL PROTECTED]>:
> StepTalk somehow doesn't seem to see my implementation of the NSExpression > class > which I compiled into libgnustep-base. The library which it is linked with > is > correct (the one _with_ the NSExpression implementation). Do I need to > recompile StepTalk too? Or do I need to implement some special thing inside > StepTalk for it to understand how to communicate with NSExpression? > StepTalk , by default, does not expose all available classes. There is a reason for that. If you would like to make a class public, you just include it in your bundle's or framework's ScriptingInfo.plist. See similar files in StepTalk sources. That is the designated way of doing it. GNUstep base is special case, similar to all GNUstep libraries. As you may have noticed, GNUstep core is set of normal libraries, not frameworks(*). Therefore there is no ScriptingInfo. As a work-around, there are "modules" in StepTalk for Foundation and AppKit. What you need it to add all new public gnustep-base classes into the Modules/Foundation/ScriptingInfo.plist. Or ... you can use hacky-way :-) as follows: Environment loadModule:'ObjectiveC'. NSExpression := Runtime classWithName:'NSExpression'. Btw. just for couriosity, are you using stexec or StepTalk interactive shell? Regards, Stefan Urbanek (*) - is there any reason why GNUstep-base is still a library, not a framework? -- http://stefan.agentfarms.net First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi _______________________________________________ Gnustep-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnustep-dev
