On Monday, June 24, 2002, at 11:30 , Harry Putnam wrote:
[..]
> One liners have a way of turning into multiliners... thats where a
> small quick script comes in.
[..]
Oh yeah - like sure....
<rant>
and the next thing you know, that script has
a function or two, then it's getting those
functions into a way that they can be loaded
into other scripts......
and one is then in some Holy Jihaud with the CPAN
about NameSpaceManagementIssues about why your
solution is really more optimized as a sub_classable
sequence.....
</rant>
Remember that this is how perl started out - a
few simple things to close the defects in sed/awk/sh -
that made coding them less easy.... { just like emacs
originally was going to close the defects in vi, before
it too became a life_style of its own. }
The only real debate between the 'perl one liner'
and the short 30 line piece of demo code - is
whether you find the one easier to play with as
you start prepping up to fix your Perl Module....
think about it - I liked an idea that
bob showalter proposed - and tested it with:
http://www.wetware.com/drieux/pbl/perlTrick/subStuff/hashDefaultsToSub.txt
then You're on the side testing an idea about the semantics
and syntax like with:
http://www.wetware.com/drieux/pbl/perlTrick/subStuff/hashDefaultsToSub.txt
and which do you like more or less....
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
