Re: [tcljava-dev] PATCH: Jacl

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

On Thu, 13 Mar 2003 21:28:14 -0700
Tom Poindexter <tpo...@ny...> wrote:

...

> Mo, *thanks* for all of your hard work in the new IO package, etc.  Jacl is
> certainly due for a release to get it on the minds of users again.
> 
> There are a few things I been looking at since your announcement, and it boils
> done to one bug and several convenience factors.  First, the bug that I see.
> 
> This has to to with my Hyde package, still not generally released because I 
> never found a good work around for the binary file IO problem

This problem was fixed by the CVS checkin on 2003-03-18. The fix will be
included in the 1.3.1 release.

> Ok, on to the nice to haves, it boils down to two patches and a wishlist.
> The first patch is to jaclsh.in.  My version adds the following:
> -the ability to use some shell parameters set outside the shell
> -run jaclsh or wisk, by checking the $0 variable, and adding the 
>  swank.jar to CLASSPATH and using the correct Shell class.
> -set a JACL_LIBRARY path to use as the library.
> -use an alternate JDK/JRE than the one Jacl was built with.
> -pass additional -D properties to the JVM.

Well, I would rather not try to cram every possible option into
the existing jaclsh script. It is provided to get folks "up and running"
quickly. No way am I going to add code to launch in multiple
JDK/JRE envs. As far as the other options go, can't  you just edit
the jaclsh script or create your own script to launch with all of
these options?

> My patch file, which also includes the TCL.OK and allowExceptions() patches,
> is below.

I have been meaning to ask you to stop doing that. Having to filter out
these patches that I have already rejected just makes it harder to
evaluate what change you are actually suggesting.

> Ok, and now for my wish list, three things: 1. fileevent, 2. lset, 3. jacllib.
> 
> Adding fileevent might be ugly until Jacl is fully converted to use 1.4's
> NIO package.  Lset would be nice, keeping in pace with Tcl 8.4.2.  
> 'Jacllib' should be able to steal much of the same code has tcllib, at least
> the code that isn't doing socket things with fileevent.  I'm also looking for
> a home for my hyde pacakge, so I have ulterior motives.  I might be willing
> to invest some time to put together some code.

Someone has to sit down and write the code. The best way to get these
wishes implemented is to sit down and start implementing them. The
NIO package could make it easier to deal with non-blocking IO, but
there is lot of Tcl C code to port even if you just use a thread that
blocks.

cheers
Mo DeJong