So, why is it that most of the solutions represented in this group tend to point to a CPAN module when the code for it isn't that hard (usually) to write? I'm not sure if using modules is a matter of "convenience" or "necessity". While the solutions shown here will most often work, they aren't practical for Joe Programmer working in the corporate world (don't flame me! LOL) who doesn't have access to install as root or install on many many servers.
Convenience. You could always write the code directly in assembly, if you really needed to, but just like it is usually easier and better to use Perl it is usually easier and better to use a module.
My point being, it might be helpful to provide a solution such as
See xxx::yyy at CPAN or my solution below
Most modules are Open Source. If you really can't install them, you could use their code directly, or indirectly through a rewrite. (And don't tell me you would then have to give away your application: very few Open Source licences require you to give the code to anyone who is not using the program. If it is in-house only you have the code.)
Daniel T. Staal
--------------------------------------------------------------- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---------------------------------------------------------------
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
