It's not clear to me whether PerlNET works thru .NET's Common Language Interface (CLI), but if it does it looks like a good idea to me (and in fact even if it doesn't it's probably a good idea.). I imagine that the reality is that .NET is going to be important over the long haul, given who's pushing it, so I like the fact that you can write components in perl using the CLI, and apparently ActiveState now. CLI is limited enough, of course, so that C# still has a preferred status, but it's an improvement over past behavior. I credit the Open Source movement for forcing this much of a concession to "openness".
Jim Eshelman ----- Original Message ----- From: "James Freeman" <[EMAIL PROTECTED]> To: "Boston Perl Mongers" <[EMAIL PROTECTED]> Sent: Monday, November 04, 2002 8:25 PM Subject: [Boston.pm] perl and .net The horror....the horror.... http://aspn.activestate.com/ASPN/Downloads/PerlNET/More Any thoughts? Jim Freeman Bioinformatics Consultant at Biogen [EMAIL PROTECTED] _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
