For those interested in the latest and greatest Inline::Tcl, here it is http://ttul.org/~rrsadler/Inline-Tcl/Inline-Tcl-0.10.tar.gz There are some major revisions in this version. I now only parse the code in the build section. Before I would execute it and then dump the available procedure, causing the inlined code to be executed twice in some situations. Also, I've finally got around to using Inline::Tcl for something usefull. This is long overdue. I've been working on a project that has spanned about two years. It involved several simulations in C, a Tk gui, and some heavy threading. I had spent a lot of time working out the Tcl interface to this library to make it callable from the TK gui. Just recently I added wanted to do another C simulation but using perl to parse a text file and run a test. It was of course much easier to do this in perl than in Tcl. Now when I wanted to run the same tests on the old simulators, all I had to do was use Inline::Tcl to call the necessary tcl procedures. I was able to make use of the hairy logic I had already worked out in Tcl rather than porting the whole thing into perl. I especially didn't want to have to redo the Tk gui. This example really makes me think that Inline has the potential to be the ultimate _GLUE_. For it to be the ultimate however, I think the Inline has to go both ways: perl procedures also callable from Tcl, sharing of data space, etc. I'm going to be dabbling at this during the summer and see what I can come up with. If anyone else has an example of how they use Inline::Tcl, let me know. It's a good way to drive development. It seems like Inline::C gets all the attention. Happy Inlining! Ryan Sadler
