On 07/04/12 16:56, John Bafford wrote: > On Apr 7, 2012, at 10:00, Tom Boutell wrote: >> .phpc is then just a convention for naming PHP files that start out >> with code - a convention that autoloaders should respect, just as they >> now respect the .php convention. "The user asked for the Monkey class, >> and I see Monkey.phpc is out there; I'll grab that with >> require_code_once." > … I think this isn't quite as simple as you make it out to be. Any autoloader > that cared about bc would have to have code like > > if(file_exists(.phpc)) require_code() else if(file_exists(.php)) require() > else HCF() > > There's a reason everyone settled around a single extension, and not the > plethora we used to have (php, phtml, php3/php4, others?). There's .php5 too :) The extension used would be just dictated by the framework. If it wants .phpc files they wouldn't test for .php files. You could even have everything at .zort files if you wanted to. But placing it as a choice of the autoloader, removes the burden of magic extensions from the engine, which is a Good Thing (TM).
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
