Re: Why change require_once? A brief explanation of motives

From: Date: Tue, 17 Jul 2007 16:12:49 +0000
Subject: Re: Why change require_once? A brief explanation of motives
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-47579@lists.php.net to get a copy of this message
Hi, Lukas Kahwe Smith wrote:
Well, except for the the fact that AllTests.php won't know where to find those classes, nothing.
You can test them by setting up your include path like always and using __autoload() or by using allfiles.php. Both can be written out once in your AllTests.php and never be touched again.
Oookay, so to run usage examples and unit tests one will still have to set up include_path. Thus everything said before about getting rid of that horrible chore is complete and utter bullshit. Case dismissed, I suppose?

« previous php.pear.dev (#47579) next »