On Tue, 2004-08-17 at 06:06, Iain McCoy wrote: > On Tue, 2004-08-17 at 14:35, Craig Dayton wrote: > > Perhaps exploring the possibility of using PerlNet a product marketed by > > ActiveState might be a cost effective solution. > > > > With PerlNet, one can define an Interface to any module on CPAN and compile > > it as a library or executable. So from a developer's prospective, a > > programmer can leverage modules in CPAN and the .NET community all within a > > single executable. Thanks to Mono this capability is now extended to the > > Unix world. No sense in reinventing the wheel is there? > Is it extended to the unix world? My understanding of PerlNet was that > it worked by interfacing between the regular win32 perl interpreter and > the MS CLR - not by compiling perl code to normal managed code. The MS > CLR interfaces that it would use are not replicated by mono, so I > suspect it doesn't work on a unix.
This is my understanding too. However a solution for reusing CPAN modules from within a .NET application on Unix would be to expose the modules functionality in a SOAP server and access it via HTTP remoting or a SOAP proxy, I am going to be giving a short talk in part on this subject at YAPC::Europe next month and will post my slides sometime afterwards if people are interested. On Windows as an alternative for reuse is to wrap the Perl module in a WIndows Script Component and access it via COM Late binding in the .NET program. Then there is perl-sharp by Rich Wareham at http://charon.ucam.org/mason/software/perl-sharp.html and PerlSharp by Joshua Tauberer at http://taubz.for.net/code/perlsharp/ both of which are intended to enable accessing Perl code directly from mono programs. /J\ http://taubz.for.net/code/perlsharp/ _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
