Ned writes:
As I said before, you really need to take a look at the code before
determining hether or not your requirements can be met.
I will be, but using it still goes against "Rhys's Rule of Programming #256
":
Don't use someone else's code, unless the time necessary to
write it yourself is going to be non-trivial. You'll have the
heartache of squeezing it into your user interface paradigm, have
the hassle of keeping up to date with their new releases, and have
the hassle of mutually incompatible copyright/license schemes.
You have better things to do with your time.
Now, from what you say, TCL looks _very good_ with a minimal amount of
heartache, but that doesn't change the fact that I don't like using other
people's code. ...
Certainly it would be useful to have an independent implementation to
find bugs in the language spec. Most people can't justify the effort,
but if you can, by all means do so and let us know how it works out!
(just make sure you write it very carefully...since bugs in the interpreter
could translate into security holes.)
Keith