RE: Re[6]: [PHP] HELP: Nested include(...)'s take relative paths not int uitively

How large can that file be? I have a func.php file that I'm putting all my reusable functions in but I can see that getting pretty large if this project starts getting eaten up with feature creep, er.., I mean additional functionality. (I know that'll never happen...;->) So how large is too large? I have about 50 constants and globals right now and it's probably going to get a little larger. At what point do you break up the files for performance versus convenience and maintainability? I read the article that someone posted the other day about "good php coding practices" and found that it contradicted a lot of what I have seen not only on php.net but in this forum. Some of what was written though made a tremendous amount of sense. Other was just common sense, like not putting function calls in loops. I think I need more coffee....... > -----Original Message----- > From: Richard Davey [mailto:rich@launchcode.co.uk] > Sent: Wednesday, February 11, 2004 9:28 AM > To: php-general@lists.php.net > Subject: Re[6]: [PHP] HELP: Nested include(...)'s take relative paths not > int uitively > > Hello John, > > Wednesday, February 11, 2004, 3:25:23 PM, you wrote: > > JWH> I hope you are also denying access to .inc files otherwise we could > view > JWH> your file as plain text. > > Please.. try ;) > > I used to call the file common.php until we had a rather large debate > about the correct naming convention for PHP include files on the PHP > Community list where various people convinced me that .inc is the > correct standard for include files. > > -- > Best regards, > Richard > mailto:rich@launchcode.co.uk > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php ****************************************************************** The contents of this e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. The views stated herein do not necessarily represent the view of the company. If you are not the intended recipient of this e-mail you may not copy, forward, disclose, or otherwise use it or any part of it in any form whatsoever. If you have received this e-mail in error please e-mail the sender. ******************************************************************