Re: Raising errors inside a constructor
| From: | Olivier Guilyardi | Date: | Tue, 17 Aug 2004 15:05:35 +0000 |
| Subject: | Re: Raising errors inside a constructor | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-32749@lists.php.net to get a copy of this message | ||
Joshua Eichorn wrote:
Well im in much the same point as you performance wise, but you do want to be careful to keep response times low, no wants to sititng for 2 seconds between clicks, though thats usually db overhead not php code parsing, unless your on something with really bad file io and very little ram.Yeah, corporate intranets use databases, heavy databases. Actually, in my case, the overhead never came from php. I had some '2 seconds between clicks' issue, and I realized it was coming from the client boxes being two slow at parsing heavy JS and HTML. With brand new desktops it just got blazingly fast !
But yea my main reason to stay away from a base class is in php4 you don't have a lot of options just extension so you don't want to waste it, if your in php5 of course you might want to look at exceptions, but there use is really a personal preference, some people just don't like using them.This is why my idea is maybe releveant for php5 as well, isn't it ? -- og