On Wednesday, April 10, 2002, at 09:20 , Jenda Krynicky wrote:
No flame war intended...
[..]
> Anyway ... to sum this all up I'd say:
>
> 1) If you are not sure you know whadaheck package means ...
> don't use it in your code.
> 2) If you introduce another package in a script ... consider
> moving the code into a separate file and truning into a fullblown
> reuseable module. You don't have to, but it might be better.
> 3) Keep your scripts short and clean. If you start getting lost
> it's more than time to consider breaking the file into several.
>
> Agreed? :-)
Quite....
I fear my grave concern is that there is no simple way to teach
new perlers that the assertion:
"but it is just a little scripting"
should ALWAYS be looked at with cynical eyes.
let alone how to help them grow the 'wisdom' (???) to see
how to start 'that little script'
with an eye on which bits will get cut out as
the supporting perl module 'functions/methods'....
So that they are ready for the second, third, fourth,....
script that will re-use the same common core code from their PM.
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
