RE: [PEAR-DEV] include vs require
| From: | Tim Thorpe | Date: | Sun, 23 Feb 2003 22:19:46 +0000 |
| Subject: | RE: [PEAR-DEV] include vs require | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13697@lists.php.net to get a copy of this message | ||
I'm not trying to start another IT[X] flamewar here. I'm just pointing
out that as PEAR grows, the probability of two simultaneously used
libraries having a common dependency increases. A minor sacrifice to
overhead seems a worthy cause if it will prevent (even small) headaches
down the road. *don't flame me* :)
-----Original Message-----
From: Rasmus Lerdorf [mailto:rasmus@lerdorf.com]
Sent: Sunday, February 23, 2003 3:51 PM
To: Tim Thorpe
Cc: pear-dev@lists.php.net
Subject: RE: [PEAR-DEV] include vs require
On Sun, 23 Feb 2003, Tim Thorpe wrote:
> It was my understanding that require_once was made part of the PEAR
> coding standard to prevent files from being re-included when
> dependencies got hairy.
Correct. But if the dependencies are not hairy, then it is pure
overhead.
-Rasmus