PHP loads everything up before it starts doing anything. It's only going
to execute the code it needs to, though, of course. I asked this
question a while ago and got that answer. The process of loading all of
the code is minimal, though, compared the actually executing the code. 

---John Holmes...

> -----Original Message-----
> From: Michael Kennedy [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 16, 2002 7:26 PM
> Subject: RE: [PHP] Newbie Question on Efficiency : Follow-up Question
> OK, if I understand C++ correctly, if I write a program and #include
> <iostream.h> or something similar and compile the program it only
> compiles with the used functions in it, right?  So, if I never use
> it leaves that function out of the final complied app.
> Does/can PHP do anything similar?  I'm always much more comfortable
> a language when I can understand how it works and I'm sure some of you
> feel the same.
> Now, I fully understand that PHP documents are not even close to being
> compiled in the traditional sense.  But, I'm wondering if it pulls all
> the necessary functions into memory when the page is accessed, then
> them when needed, or does it pull the whole include()d file into
> and just combine the whole mess together into one big memory heap and
> run like that?
> My gut tells me that it's the second one, but I'm just wanting to be
> sure.  Of course, the answer likely won't make a single difference in
> life, but I'm just curious...  Also, I hope the above question isn't
> stupid.  I do have a habit of thinking about something for a while and
> then having it suddenly hit me later that the answer is simple very
> trivial.  Ah, well...
> Thanks for humoring me.
> Michael
> -----Original Message-----
> From: Monty [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 16, 2002 5:44 PM
> Subject: Re: [PHP] Newbie Question on Efficiency
> If you have have a large number of functions, it might be better to
> separate
> them into a few files that you can include as needed. I use one file
> that
> contains functions needed by every page. I have a few other files that
> contain functions that aren't needed by every page, so, I include them
> only
> on pages that need them. But most functions go in the main include
> used
> on every page.
> Separating them will also minimize some overhead if you have a lot of
> functions. Otherwise, if your include files aren't War & Peace in
> length,
> one include file is fine.
> >>>> [EMAIL PROTECTED] 07/16/02 04:59PM >>>
> > Hello everyone, I'm a newbie and have a question on style that I've
> not
> > seen addressed anywhere.  I have a large number of frequently used
> > functions that I'm trying to find a good way to organize.  The
> > I'm thinking of using is to simply create a .php file called, for
> > example, functions.php.  Then, just include the file at the top of
> each
> > page that needs any of the functions, and just call them as needed.
> My
> > question is this- if that file gets very large with tons of
> > functions, is that an inefficient method?  I'm not entirely clear on
> how
> > PHP is parsed and passed to the client.  I assume it would be best
> > divide up the functions into multiple files (ex. dbfunctions.php,
> etc.),
> > but is that still the best method?  Basically, I'm just curious on
> > you guys handle things like this.
> >
> > Thanks in advance.
> > Michael Kennedy
> >
> --
> PHP General Mailing List (
> To unsubscribe, visit:
> --
> PHP General Mailing List (
> To unsubscribe, visit:

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to