in reply to Perl compiler for .NET - anyone knows anything about it?

I remember hearing about this a few years ago. A bit later I heard that they got it running, and found that what they got running was way too slow to be useful. Perl's highly dynamic internal opcodes are not a good match for C#'s internal bytecode engine.

I believe that ActiveState sells a product that links a native C version of Perl into C#. I've not heard anything more (and I'm not sure that they do - I don't use Windows or C# so don't rely on me for those products).

But if you want a scripting language built into C#, I've heard that IronPython is a fairly complete implementation. I consider Python and Perl pretty similar in capability (if not "feel"), so that might meet your needs.

  • Comment on Re: Perl compiler for .NET - anyone knows anything about it?

Replies are listed 'Best First'.
Re^2: Perl compiler for .NET - anyone knows anything about it?
by techcode (Hermit) on Sep 03, 2005 at 10:20 UTC
    No I'm not looking at just any scripting language built into C# - I actually consider Perl to be much more than just scripting language :)

    Damn I can do so crazy (in good sense) things in Perl that I could only dream off in say C++ (or code half a day to accomplish those 5 minute things).

    The thing that I plan to work more on is GUI (desktop apps) programming with Perl as I'm now mostly into web programming. The reason for sticking to just web programming is partly that user needs to go through hassle of installing Perl (on Windows boxes) just to run my application.

    Yes I know about PAR and other similar solutions - but having .NET IL code would be somewhat more secure than shipping your source...

      What you are looking for is PDK, namely PerlNET.

      The Perl code is not compiled into .Net IL (since that was too slow), but you can create a DLL that (from the outside) will look just like any other .NET dll and you will be able to use .Net stuff from Perl and Perl stuff from .Net. Been there, done that. All you need apart from the generated DLL when shipping the app are two more DLLs.

      Jenda
      XML sucks. Badly. SOAP on the other hand is the most powerfull vacuum pump ever invented.