> My problem with MODULES is you must also install them everywhere, if you
> use one that is outside the default installation.
> Of course the PASRE is not in the category with Activeperl.

 I agree with you on the problem of having to distribute modules with your
code. I guess you could use perl2exe or an interesting idea along the lines
of Java JAR files is the PAR project :

 http://search.cpan.org/author/AUTRIJUS/PAR/

 At least with ActiveState on Win32 servers I can PPM the modules down (When
the server isn't in our DMZ!). I look after a mostly HPUX / Solaris
infrastructure and when HPs bundled compiler can't even compile Perl then it
begins to get interesting. HPUX 11i is better because they bundle an
ActiveState build of 5.6.1 with the OS and it's compiled with gcc. That
means I at least have a chance of building DBD::Oracle and DBD::Informix
amongst others. Actually I'm getting quite adpet at it but the road here has
been winding ;-)

> I also find it annoying, that all modules are NOT run with -w and strict
> enforced.  Geez, if you gonna make it public and all shouldn't ya take the
> time to crush the undefined, and other annoyances?

Yep I'd agree 100%. I have created a few in house specific modules which I
may consider releasing into CPAN but not until they run with warnings on and
under strict. (Which most do from the start)

> Though I agree, if the module is easy to use.  And does what you want,
> then
> by all means use it.  But if you only need to write
> three lines of code that will get the job done for 99% of the work.  Is it
> worth hunting for the right module and learning that module
> to get it done days later instead of in 10 minutes?  It depends.

 CPAN and the wealth of third party modules is one of the reasons that keeps
me writing Perl (as well as it being fun !). I know C++ and a little Java
but I have to start from scratch with those languages. I saw a post recenlty
on the Use Perl site stating that the C++ comunity in particular would like
to get their own version of CPAN (CCAN or CCppAN ?) going and I for one
would welcome it. If nothing else it helps to build and develop the
community and for me that's one of the best things about Perl - people, like
those who contribute to CPAN, usenet and lists like these, giving their time
and code to help out others.

As I'm sure we all remember "There's more than one way to do it" and as a
C++ developer I respected once told me when I asked if I was doing sockets
correctly "If it works you're doing OK." I use modules for alot of stuff,
but I also write hundreds of lines of my own code.

Whew that went WAY longer than I anticipated. Normal service will be resumed
shortly ... ;-)

Paul



_______________________________________________
ActivePerl mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to