Re: [tcljava-dev] [Incr Jacl]: How to proceed?

[Christian K. <chr...@so...>]

Hello,

> > A nice package name could be "tcl.incr", so the sources would
> > be put into .../src/jacl/tcl/incr. The jar file containing
> > all the Incr classes should probably be called incr.jar.
> > And the loadOnDemand() inside Interp should be removed again.
> 
> I don't know if we should even put the incr Jacl code
> in the same tree as Jacl. Why not have another tree
> with its own ./configure and so on? That is what
> Bruce did with Swank (Tk via Swing).

I think it is less effort to populate the existing tree
instead of creating a new one. And when some day IncrTcl
will be integrated into the Tcl language, we have the
stuff already there :-)

Anyway, does the Swank sources belong to tcljava? Or do
they have their own project? Or do they have their
own tree below tcljava/src and you can give a
command line option --enable-swank to configure?

> > But how would the new classes be loaded into the Jacl interpreter?
> >From the users point of view, it should be as easy as
> "package require IncrTcl".

You mean "package require Itcl", don't you?

> Your implementation would most likely extend
> src/tcljava/tcl/lang/Extension.java.[...] The hard part
> might be getting "package require ..." to work
> when the ... package is in a .jar like incrtcl.jar.
> I think the best way to implement that is to use
> the manifest file to list what Tcl packages are
> available in a given .jar file and the java class
> name.

This looks like I should take a break on the Incr sources
and should spend some time on the package command...
I had some hopes that I can work around it, but they
are gone now.

Greetings, Krischan
-- 
Christian Krone, SQL Datenbanksysteme GmbH
Mail mailto:chr...@so...