On Sep 17, 2005, at 8:29 AM, Randal L. Schwartz wrote:
There are days when I wanna answer that as "3". :)
That's exactly how I felt when I asked this. :)
... time passes ...
And my script keeps getting bigger...
And I was just going to leave that as a joke answer, but on serious
reflection, your CGI "scripts" should be nothing more than
configuration and method calls against a testable module.
Ok that makes sense. I sort of did this back in the days of using
"Libraries" of sub-routines but I've never really pushed myself over
the creating my own modules hump... I played a bit with an example
module I found online the last couple days and maybe I'm not as far
away from doing this as I thought... I'm not quite ready for
CGI::Prototype though. Randal, you're so far ahead of me I don't think
I can even see your dust, but I sure do enjoy following your footsteps.
On Sep 17, 2005, at 6:38 AM, Chris Devers wrote:
When it gets to the point that you find it hard to maintain that way.
Yeah, I think I've reached that point.
This threshold will be different for different people.
When to start breaking things into smaller scripts -- just as when to
start breaking things into smaller subroutines -- is largely a matter
of
personal preference, based on your own personal experience with writing
and maintaining your code over time.
I guess the thing to do is to move my sub-routines into modules, and
create smaller scripts to handle specific user requests. This would be
more efficient (regarding server load) than one big script wouldn't it?
Thanks to all for the good advice,
--
Bill Stephenson
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
