diff options
Diffstat (limited to 'README')
| -rw-r--r-- | README | 32 |
1 files changed, 31 insertions, 1 deletions
@@ -21,7 +21,7 @@ dual ported objects to ensure that the execution time does not reflect the semantic of the language :) ------------------------------------------------------------------------------ -WHERE JIM IS USEFUL? +WHEN JIM CAN BE USEFUL? ------------------------------------------------------------------------------ 1) If you are writing an application, and want to make it scriptable, with @@ -30,6 +30,11 @@ with a big system. You can just put jim.c and jim.h files in your project and use the Jim API to write the glue code that makes your application scriptable in Jim, with the following advantages: +- Jim is not the next "little language", but it's a Tcl implementation. + You can reuse your knowledge if you already Tcl skills, or enjoy + the availability of documentation, books, web resources, ... + (for example check my online Tcl book at http://www.invece.org/tclwise) + - Jim is simple, 10k lines of code. If you want to adapt it you can hack the source code to feet the needs of your application. It makes you able to have scripting for default, and avoid external dependences. @@ -79,6 +84,31 @@ scriptable in Jim, with the following advantages: implementation ;). -------------------------------------------------------------------------------- +HOW BIG IS IT? +-------------------------------------------------------------------------------- + +Jim compiled with -Os is 65k currently. Still it lacks core commands +that will make it a little bigger, but not too much... only what's +strictly required will end inside the core, the rest will be implemented +as extensions. + +Note that the actual Jim core is much smaller, if you strip away commands. +If you can do without [expr] (that's big about code size), and some +other command you may probably end with a 40k executable. + +-------------------------------------------------------------------------------- +HOW FAST IS IT? +-------------------------------------------------------------------------------- + +Jim is in most code faster than Tcl7.6p2 (latest 7.x version), +and slower than Tcl 8.4.x. You can expect pretty decent performances +for such a little interpreter. + +If you want a more precise measure, there is 'bench.tcl' inside this +distribution that will run both under Jim and Tcl, so just execute +it with both the interpreters and see what you get :) + +-------------------------------------------------------------------------------- HOW TO COMPILE -------------------------------------------------------------------------------- |