Phil Tomson wrote: > > Brian, > > I just read your article in the Perl Journal about the Inline module - > very cool! > > I noticed at the end you mehtion that you want to support other > languages as well including C++, Fortran, Pascal and Python. In the > case of other interpreted languages, like Python, how (on a very high > level) would this work? Would you invoke the interpreter for Python and > then send the code? How to interface with the variables in Python? I'm > just curious because I would like to start using Ruby ( > http://www.ruby-lang.org - check it out, very cool OO scripting > language, much better than Python IMHO), but we have a lot of legacy > Perl code around that management still wants us to use and I'm thinking > that Inline might be a good way to start transitioning to Ruby. Inline::Python has been implemented by Neil Watkiss <[EMAIL PROTECTED]> It is actually done by _compiling_ C bindings instead of using a truly interpreted model. That is because Inline.pm is designed for compiled languages. I plan to add interpreted language support in the very near future. Then Neil will do a better implementation of Python. This week I am releasing Inline version 0.30 which is a very major revision. The most important feature is adding support for writing new Inline Language Support Modules. The C support is completely encapsulated in Inline::C. Neil has written Inline::Python and Inline::CPP. I have also written Inline::CPR for embedding Perl in C. Next in line are: Inline::Java Inline::Bash Inline::Fortran and yes, Inline::Ruby Actually, I'm trying to encourage the "Inline community" to start working on these. You can join the effort by subscribing to [EMAIL PROTECTED] (send email to [EMAIL PROTECTED] ) Cheers, Brian -- perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf ("Just Another %s Hacker",x);}};print JAxH+Perl'