Re: [tcljava-dev] [Incr Jacl] Almost done

[Mo D. <md...@cy...>]

On Tue, 24 Apr 2001, Christian Krone wrote:

> Hello,
> 
> > > I think the first step should be to integrate the needed
> > > changes of Jacl sources into the 1.3 CVS tree.
> 
> I have attached the diffs for the following java files:
> Interp.java, NamespaceCmd.java and Var.java.
> Also a patch for the startup script init.tcl is attached.
> And finally I modified Interp.test of the jacl test suite,
> where some forgotten braces used to mangle the test summary.

I just checked in the resolver related changes.

> > > Oh yes, and finally the class JaclLoadsItcl is new :-)
> > Humm, I am not sure about this "JaclLoadsItcl" thing.
> > Is it a just a hack like the way the java package
> > is provided by Jacl?
> 
> Yup, it was. But isn't needed anymore, since when the Java
> package is available, you can use an ordinary java::load
> to get the Itcl package (no bootstrapping problem as for
> the Java package).
> 
> I still have the feeling that it would be best to have
> this "package provide Itcl" line inside of a pkgIndex.tcl
> file somewhere, but I have no idea where I should put it...

Yeah, we need to come up with a way to let the Tcl class loader
know where the pkgIndex.tcl files for a given .jar file live.
Then we just look for a pkgIndex.tcl file in each .jar file
we find and source it.

> > Yeah, it would be better to fix the tcl.lang package to
> > export all the interfaces you need.
> 
> For the same goal we should tear off Namespace from the
> NamespaceCmd class. Most (or all) of the methods of
> NamespaceCmd, which should be public, are methods
> belonging to the Namespace class.

I don't have a problem with that approach. The catch is that
if we make Namespace a public class we need to also implement
that same API for Tcl Blend. In fact, we really need to do
that for these new Interp APIs so we can add then to the
docs. I am going to add a TODO for that right now just
do I don't forget.

> Would be tcljava/src/incrjacl then the correct place to use?

That sounds just fine.

Mo DeJong
Red Hat Inc