Thanks Mathew, Jason and Joseph for the reply.
I never thought that having a large function could be a bad thing.
I'll keep your tips in mind when writing functions from now on. Fortunatly,
the function I was refering to that was 100 lines is a one time use
function. It's only used to setup the backend for my script, and after that
it's never called during normal use. (the user would have to delete the
configuration file in order for the function to be called again.)
Theoreticly, I could take out a lot of "check and balance" type of code, and
get it done in half the lines, but realisticly that wouldn't be too good for
the overall setup of the script, since it is defining the core of the
application.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
