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.
Phil,
Hi again. I thought you should know that I picked up a copy of
"Programming Ruby" this weekend. I'm very excited about this language.
It's like taking the best parts of Perl, Python, and Smalltalk and
making something that Java only wishes it could be.
Expect Inline::Ruby to be the next ILSM. I'm really happy about the way
Neil Watkiss' Inline::Python turned out. We came up with an internal
model that supports interpreted languages as well as compiled ones.
Since Ruby's internals look pretty clean, it should come together pretty
quickly.
Let me know if you want to help out. I would like to see other people
authoring (and supporting) new ILSMs. Neil and I will always be
available to help out on the mailing list ([EMAIL PROTECTED]).
BTW, I think Inline::Ruby is kind of backwards. Inline.pm helps Perl
programmers make use of old legacy C code. Ruby should have an inline
facility for making use of old legacy Perl code!
Brian
>
> Thanks.
>
> --
> Phil Tomson
> Sr. Software Engineer
> Cypress Semiconductor
> Beaverton, Oregon
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
