Re: [PHP] Just for fun:

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

[PHP] Just for fun:

Here is a question, just for fun: What is the biggest function (In terms of line count) you have ever written? I just finished one that is 100 lines long. That is by far my biggest It's a script initialization function that sets up database connectivity, creates all tables necessary for

RE: [PHP] Just for fun:

-Original Message- From: Jason Bell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 8:32 PM To: PHP Users Subject: [PHP] Just for fun: Here is a question, just for fun: What is the biggest function (In terms of line count) you have ever written? I just finished one

RE: [PHP] Just for fun:

Lead Programmer - pulseaday.com At 08:40 PM 9/20/2001 -0400, Matthew Loff wrote: -Original Message- From: Jason Bell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 8:32 PM To: PHP Users Subject: [PHP] Just for fun: Here is a question, just for fun: What is the biggest

RE: [PHP] Just for fun:

When you find yourself writing HUGE functions, it may be better to split it into smaller, more clearly defined functions or classes and do it that way... I totally agree i tend to split my class functions into user (public) and private (helper) functions which does tend to keep all the