While I was shifting through various TCL scripts trying to get a feel for it, I had an idea.
How about someone write a module that could parce basic mirc script (Basic as in support for ON events like on join, and things like that)? I know jack all about TCL, and the simplist things like voicing someone on a channel takes LOTS of code compared to mirc script.
Just an idea.. You could like save a .mrc in the scripts directory and set the module to read it like .mircscript +scripts/onjoin.mrc or something
The differance between eggdrop and mirc are so large, it could probably deserve it's own place in a library.
The first, aand most major point, is that eggdrop is not a client. Clients use user interaction, and provide easy to use interfaces, for day -to-day use on IRC, while eggdrop, is autonamous, and has to rely solely on a pre-programed set of instructions (modules or Tcl scripts).
I reality, mIRC script, is not a programming language. It's a basic set of instructions, using the commands provided for normal IRC interaction by the user.
Instead of totaly re-writting the parser, and creating a whole new language, like they should have done, they simply added, and added onto a rubbish parser.
A programing language, is supposed to be based, on a few simple staments, from which, the language can build itself. Then, the language should provide simple functions, fro interaction in other places.
In mirc, these simpelm statments exist, only to be converted into somthing new, by adding stupid options to them.
mIRC script, in this case, would be very hard to impliment, as a lanugage to eggdrop.
Tcl is very easy to learn, allmost as simple as mIRC script.
Once you know the structure of the code, it's a simpel case, of learning the arguments used in commands, which can be done on the go.