Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Edward Vermillion
On Apr 30, 2006, at 8:07 PM, Richard Lynch wrote: Instantiating an object does have some extra overhead that the static call bypasses. How much overhead depends on the complexity of the object, I would predict that it's mainly in its constructor and any parent constructors. Well there's a

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread chris smith
On 5/1/06, Edward Vermillion [EMAIL PROTECTED] wrote: On Apr 30, 2006, at 8:07 PM, Richard Lynch wrote: Instantiating an object does have some extra overhead that the static call bypasses. How much overhead depends on the complexity of the object, I would predict that it's mainly in its

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Jochem Maas
Edward Vermillion wrote: On Apr 30, 2006, at 8:07 PM, Richard Lynch wrote: Instantiating an object does have some extra overhead that the static call bypasses. How much overhead depends on the complexity of the object, I would predict that it's mainly in its constructor and any parent

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Edward Vermillion
Thanks guys! I guess it comes down to Don't do anything stupid and you should be fine :D I'm just still in the design stage, and since my past practice was write/figure out what you did wrong why it doesn't work like it should/rewrite, I'm trying to cover as many bases as I can from the

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Richard Lynch
On Mon, May 1, 2006 8:25 am, Edward Vermillion wrote: What I was mainly thinking of though, what kind of hoops does PHP jump through to take a class, that I assume it's holding in memory, and make an object out of it, aside from the constructor? Is it doubling the memory consumption, or more,

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Jochem Maas
Richard Lynch wrote: On Mon, May 1, 2006 8:25 am, Edward Vermillion wrote: What I was mainly thinking of though, what kind of hoops does PHP jump through to take a class, that I assume it's holding in memory, and make an object out of it, aside from the constructor? Is it doubling the memory

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Edward Vermillion
On May 1, 2006, at 3:53 PM, Richard Lynch wrote: On Mon, May 1, 2006 8:25 am, Edward Vermillion wrote: What I was mainly thinking of though, what kind of hoops does PHP jump through to take a class, that I assume it's holding in memory, and make an object out of it, aside from the

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread chris smith
On 5/2/06, Edward Vermillion [EMAIL PROTECTED] wrote: On May 1, 2006, at 3:53 PM, Richard Lynch wrote: On Mon, May 1, 2006 8:25 am, Edward Vermillion wrote: What I was mainly thinking of though, what kind of hoops does PHP jump through to take a class, that I assume it's holding in memory,

Re: [PHP] OOP Static Functions vs. Objects

2006-05-01 Thread Edward Vermillion
On May 1, 2006, at 8:56 PM, chris smith wrote: Depending on your content you could cache some of it to static files.. http://pear.php.net/packages.php?catpid=3catname=Caching (I'm sure there are tons more packages to do this as well).. Yeah, that's what I'm looking at right now, although

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Jochem Maas
Edward Vermillion wrote: I'm still trying to get my head around all the OOP stuff and was wondering if there is any basic difference between calling a static function as opposed to creating an object, in situations where both methods will do the same thing for you. Is there any overhead to

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Edward Vermillion
On Apr 30, 2006, at 10:10 AM, Jochem Maas wrote: Edward Vermillion wrote: I'm still trying to get my head around all the OOP stuff and was wondering if there is any basic difference between calling a static function as opposed to creating an object, in situations where both methods

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Jochem Maas
Edward Vermillion wrote: On Apr 30, 2006, at 10:10 AM, Jochem Maas wrote: Edward Vermillion wrote: I'm still trying to get my head around all the OOP stuff and was wondering if there is any basic difference between calling a static function as opposed to creating an object, in

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Edward Vermillion
On Apr 30, 2006, at 10:45 AM, Jochem Maas wrote: CVS or subversion (and 3 weeks intensive study of what branches are) might be of help to you - not for the faint-hearted though! Been reading the subversion manual for the past three days... ;) (I'm a slow reader) Ed -- PHP General

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Jochem Maas
Edward Vermillion wrote: On Apr 30, 2006, at 10:45 AM, Jochem Maas wrote: CVS or subversion (and 3 weeks intensive study of what branches are) might be of help to you - not for the faint-hearted though! Been reading the subversion manual for the past three days... ;) (I'm a slow

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Stut
Jochem Maas wrote: me I'm just slow - I still on 'how the f*** do I use branches in CVS' after using it for 18 months+; and I haven't even begun to look at subversion yet :-P I strongly suggest you skip branches in CVS and go straight to subversion. I've been using CVS for years and have

Re: [PHP] OOP Static Functions vs. Objects

2006-04-30 Thread Richard Lynch
Instantiating an object does have some extra overhead that the static call bypasses. How much overhead depends on the complexity of the object, I would predict that it's mainly in its constructor and any parent constructors. I can't speak to differences in PHP4/PHP5 in this specific regard, but