Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: Re: What do you think about ActiveState's Visual Perl .NET??

by Anonymous Monk
on May 30, 2002 at 22:59 UTC ( #170544=note: print w/replies, xml ) Need Help??


in reply to Re: What do you think about ActiveState's Visual Perl .NET??
in thread What do you think about ActiveState's Visual Perl .NET??

Doesn't the PerlNet component just link the native Windows version of Perl with .NET with a bit of glue to allow them to call each other? Perl is not running on the .NET VM, is it?

If so, then if you use Perl on .NET it won't be portable to other platforms (like Mono, or Parrot's .NET emulation). Ironic, ain't it?

  • Comment on Re: Re: What do you think about ActiveState's Visual Perl .NET??

Replies are listed 'Best First'.
Re: Re: Re: What do you think about ActiveState's Visual Perl .NET??
by demerphq (Chancellor) on May 31, 2002 at 08:34 UTC
    Doesn't the PerlNet component just link the native Windows version of Perl with .NET with a bit of glue to allow them to call each other?

    Yes.

    Perl is not running on the .NET VM, is it?

    No.

    then if you use Perl on .NET it won't be portable to other platforms

    Er, maybe im confused by what you mean by this, but the previous two answers (which you asked rhetorically, so you know this already) clearly indicate that the perl code you write using the .NET IDE, so long as it doesnt utilize other .NET features should be just as (non)portable as the same code written using Emacs, Ultraedit or the commandline. Why should the fact that youve used the activestate IDE change anything?

    Yves / DeMerphq
    ---
    Writing a good benchmark isnt as easy as it might look.

      The point was that if you actually use the ability to interoperate between .NET and Perl, then you have used something that is specific to the Microsoft implementation of .NET which is not supported by other versions of the CLR.

      Therefore that is a non-portable thing that is easy to take advantage of. (And is one of Microsoft's platform lock-in tricks even while they make a great song and dance over being platform independent.)

      Now if you use Visual Studio to write Perl and you don't interoperate with .NET in the resulting code, then you have no portability problems. But if you use the PerlNet component, expecting to take advantage of the features that Microsoft lists (including portability), then you have fallen for a bit of a sham.

        My understanding of these matters is that if you write .NET specific code then there is no reason to expect cross-platform compatibility. So I dont see that its a sham. Its kindof like writing code that uses System V IPC rouines and expecting it to run on a Win32 box.

        Im sure that when Microsoft said portability they meant from one Win32 Box to another ;-)

        And you dont really believe anything that MS says anyway do you?

        Yves / DeMerphq
        ---
        Writing a good benchmark isnt as easy as it might look.

Re: Re: Re: What do you think about ActiveState's Visual Perl .NET??
by tlhf (Scribe) on May 30, 2002 at 23:37 UTC
    Well, to be honest, it might, I don't know a massive amount about it. I played with it a bit on my pc, and it worked fine without any noticible deviations from .Net, so I assumed that's how it worked.

    Do you have any urls where I could read up on this?

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://170544]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (4)
As of 2021-10-21 23:33 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My first memorable Perl project was:







    Results (85 votes). Check out past polls.

    Notices?