in reply to Re: Re: Re: ActiveState Perl for .NET
in thread ActiveState Perl for .NET

My understanding (based on the little technical info provided during the .NET Launch party in Las Vegas last month) is that unmanaged code allows you direct contact with the hardware as opposed to the CLR handling that low level happiness. The implication being that you are responsible for your own memory mangagment, garbage collection, etc. (primarily an issue for C and C++ folks!)

Does this sound like it lines up with your understanding, or am I totally off-base ;).

-Brett

  • Comment on Re: Re: Re: Re: ActiveState Perl for .NET

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: ActiveState Perl for .NET
by Elian (Parson) on Apr 19, 2002 at 18:57 UTC
    Yup, that's it. Use a single piece of unmanaged code and all security and stability guarantees are shot to hell. OTOH, it lets you do things that .NET either can't, or can't do efficiently.