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.
|Replies are listed 'Best First'.|
Re: Re: Re: Re: Re: What do you think about ActiveState's Visual Perl .NET??
by demerphq (Chancellor) on May 31, 2002 at 11:35 UTC
by Anonymous Monk on May 31, 2002 at 23:13 UTC