NYCPHP Meetup

[Phil Powell]

I'm doing something similar to that in my PHP app structuring.  I will 
have one front-end PHP script, an "index.php", that will require and 
include .inc.php files that contain classes as well as one .inc.php that 
contains my global variables and functions.  Sort of a procedural - OO 
blend.  It's honestly the best way for me to do app development that, 
well, works for me and ultimately... works.

Phil

bpang at bpang.com wrote:

>Thanks to all for your helpful responses.
>
>Chris, I am exactly at that point where I have moved and separated (most)
>everything out to functions in included files.
>
>A lot of the stuff I have, I have been able to reuse across multiple sites.
>For example, a whole collection of database functions, such that I never
>actually call mysql_query directly in my code.
>Or another that builds select menus for me.
>
>When I have a chance, I will certainly try some of the suggestions that
>have been posted. Between all the responses, it's as though new light has
>been shed on the situation.
>
>:)
>
>Lastly, are there any performance gains with OO over proceedural?
>_______________________________________________
>talk mailing list
>talk at lists.nyphp.org
>http://lists.nyphp.org/mailman/listinfo/talk
>
>  
>


-- 
Phil Powell
Web Developer
  ADNET Systems, Inc.
  11260 Roger Bacon Drive, Suite 403
  Reston, VA  20190-5203
Phone: (703) 709-7218 x107   Cell: (571) 437-4430   FAX: (703) 709-7219
EMail:  Phillip.Powell at adnet-sys.com      AOL IM: SOA Dude