[tcljava-dev] [Fwd: CallFrame and interp.newCallFrame() questions.]
Brought to you by:
mdejong
From: Neil M. <ne...@cs...> - 2001-11-20 21:56:38
|
Hmm... lost my permission to post this, but hopefully it should make it through this time. -------- Original Message -------- Subject: CallFrame and interp.newCallFrame() questions. Date: Tue, 20 Nov 2001 21:45:36 +0000 From: Neil Madden <ne...@cs...> Organization: University of Nottingham (Computer Science Undergrad) To: tcl...@li... Looking through the source code for Jacl, I notice that the CallFrame class starts with the message "This class can be overridden to provide new variable scoping rules for the Tcl interpreter.". Similarly, the Interp.newCallFrame() method has the message "This method can be overridden to provide debugging support". Who are these comments meant for? The CallFrame class has package-only access, and Interp.newCallFrame() is protected, so you could only subclass them (and override their behaviour) if your class is in the tcl.lang package. So, is this functionality for overriding the default behaviour meant only for people building their own private Jacl distro, or is there some other way to register your own CallFrame class with Jacl? I ask because I am playing around with writing a simple OO extension for Jacl (with some neat features though), and it would be useful for me to define a new CallFrame for use with methods on my objects. I don't want to put any of my classes in the tcl.lang package, as that would just be messy. Anyone know? Neil |