[PHP] PHP OOP x Procedural Performance - Conclusions

2003-05-30 Thread William N. Zanatta
First of all. Thanks everybody for the feedback. It was very precious to hear from you. So, there's no big differences unless we're working with heavy processes. Even in this case, the performance seems to be very good in both practices, thus I'll keep OOP. My OOP concepts are not really s

Re: [PHP] PHP OOP x Procedural Performance

2003-05-30 Thread Ernest E Vogelsinger
At 04:05 29.05.2003, William N. Zanatta said: [snip] > It is a known issue that function calls are expensive for the processor. > > The OOP let us better organize the code but, thinking in function (or >method) calls it may be more expensive than in the proc

RE: [PHP] PHP OOP x Procedural Performance

2003-05-29 Thread Jay Blanchard
[snip] It is a known issue that function calls are expensive for the processor. The OOP let us better organize the code but, thinking in function (or method) calls it may be more expensive than in the procedural form. My question is, has anyone made any tests regarding the performance of OO

Re: [PHP] PHP OOP x Procedural Performance

2003-05-29 Thread Ray Hunter
yes, the bottom line is code reuse...that is why there is oop. So that a developer can always reuse code saving money on development and thus if speed is an issue then adding more hardware. -- Ray On Wed, 2003-05-28 at 20:05, William N. Zanatta wrote: > It is a known issue that function calls

[PHP] PHP OOP x Procedural Performance

2003-05-29 Thread William N. Zanatta
It is a known issue that function calls are expensive for the processor. The OOP let us better organize the code but, thinking in function (or method) calls it may be more expensive than in the procedural form. My question is, has anyone made any tests regarding the performance of OOP vers