Re: [tcljava-user] Reasons for using JACL?
Brought to you by:
mdejong
From: Tom P. <tpo...@ny...> - 2006-11-27 21:09:00
|
On Mon, Nov 27, 2006 at 09:11:52PM +0200, Kristoffer Lawson wrote: > On Mon, 27 Nov 2006, Patrick Finnegan wrote: > > > It seems to me that the primary purpose of JACL is to allow java programmers > > write procedural non object orientated code that will run under a JVM and > > perhaps allow non java programmers to access or administer the application > > through a simple script interface . Are there any other reasons why Java > > programmers would embed JACL or indeed Jython in a Java application rather > > then writing everything in pure Java? > > I've used it in the traditional good scripting manner. Ie. I have a core > written in Java which is then scripted via some Jacl scripts. > > Pure Java is quite simply inferior when it comes to writing tests or for > dynamic stuff from the CLI or whatever. In fact, Java is inferior to Tcl > for the core stuff as well, but I have no say in that matter. > I think you could apply most of the same reasons why one woud use Tcl/C instead of pure C. Write less code. My use of Jacl is inverted from Patrick's use: I use Jacl driving Java objects. Most of my Jacl usage is: Prototyping, Integration and unit testing (JUnit is simply the wrong approach, IMHO) Lightweight applications Administrative tasks in larger applications More to come in the next few weeks, watch this space. -- Tom Poindexter tpo...@ny... |