Re: [tcljava-dev] Should-be made public most of methods in tcljava (was: Swank 1.0 bugs)

[Neil M. <ne...@cs...>]

Maurice Diamantini wrote:
> 
> 
> Also, I'tried to make a personnalised shell based on
> tcl.lang.Shell
> But it doesn't worked until I make my personnalised MyShell
> as a class of the tcl.lang package (but letting it into
> my starting project. This is a very bad design for me to be
> constraint to modify the internal jacl packages).
> 
> So probably there is to much non public methods
> in tcljava ?
> Is there any inconvenient to make these public ?
> 

This is something I would also like to be addressed. I've run into problems a
couple of times with access control, for instance, I was looking at the
feasibility of implementing Itcl or similar for Jacl, but stopped when I ran up
against problems adding my own CallFrame object. Because of access control, you
had to create a new CallFrame object in tcl.lang, and also duplicate some of the
Interp code to get it to work. The problem is that while a lot of this may be
private in the C-tcl, it is easy to get around that, whereas in Java, it isn't
:-(

Neil.


-- 
package r Tkhtml;package r http;pack [scrollbar .v -o v -co {.h yv}] -s right\
-f y;pack [html .h -ys {.v set}] -f both -e 1;bind .h.x <1> {eval g [.h href %x\
%y]};proc g u {set t [http::geturl $u];.h cl;.h p [http::data $t];http::cleanup\
$t;.h co -base $u};g http://mini.net/tcl/976.html;proc bgerror args {};# NEM :-)