>>>> If not what is the preferred way to handle >>>> errors? hijacking #doesNotUnderstand in the Object class ( including >>>> #halt and company )? >>> >>> Hijacking SystemExceptions.UnhandledException>>#defaultAction sounds >>> better. >>> >>> Even better would be to define #debuggerClass in the superclasses that >>> your scripts are supposed to subclass. The #debuggerClass will be >>> sent the class method #open:. >> >> What kind of class is #debuggerClass supposed to return? Of course I >> could simply make a class with only #open but I'd like to use the proper >> superclass for this situation to avoid breaking potential future gst >> versions. > > Yes, any class with #open: will do. What exactly does #open do? Assuming I use a c function as #open in the base class do I then get this function called whenever there is a run-time problem? > This is wrong indeed, you found a bug in GNU Smalltalk. :-( > > I suggest that you base your application on the master branch of the > GNU Smalltalk git repository, where I have fixed the bug. The next > release will be out soon, so it is stable and has new features, some > of them useful for bindings. If you prefer, I can backport to 3.0 or > 3.1 though. Not a problem. Fixed it right now by using OOP pObjNil = gst_eval_expr( "nil" )
This should be the same as the interpreter nil. Works with that so far. -- Yours sincerely Plüss Roland Leader and Head Programmer - Game: Epsylon ( http://epsylon.rptd.ch/ , http://www.moddb.com/games/4057/epsylon ) - Game Engine: Drag(en)gine ( http://dragengine.rptd.ch , http://www.moddb.com/engines/9/dragengine ) - Normal Map Generator: DENormGen ( http://epsylon.rptd.ch/denormgen.php )
signature.asc
Description: OpenPGP digital signature
_______________________________________________ help-smalltalk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-smalltalk
