<html>
<body>
<FONT face="Verdana, Arial, Helvetica, sans-serif" size=3><BR>
<P><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3>I imagine writing a language translation layer for perl on top of JVM would be a major, major project. I'm sure a worthy one, but since I don't program in Java I'll just have to let it go by. By the way, has this been done for any other language? I think the java people may feel like that since they're already giving you platform independance, if you want to use the JVM just use it via Java.</FONT></P>
<P><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3>But I do an awful lot of work in C# on the .NET platform, yet I still miss the convenience of the perl syntax and language constructs.</FONT></P>
<P><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3>Also I'm impressed with the facilities and even coaching MS has provided for those that want to instantiate a new language binding on top of the CLI. That's why, I'm sure, the Python people were able to succeed.</P>
<P>Most recently, the Monad group has made progress and has released Windows Power Shell <A href="http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx" target=_blank>http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</A> which is a new way of lashing together .NET CLR objects to do useful work using this new shell scripting language.</P>
<P>But for me, I'm more interested in perl as a programming language, because it is so expressive (you get a lot of bang for each line of code you write) and it is precisely this linking and pipelining behavior that seems like would be a good fit on top of the .NET API.</P>
<P>Just my three cents...</P>
<P></FONT></P></FONT>
<br>
</body>
</html>