Re: [Pre-RFC] Pure-code source files via .phpc extension

>> I think this adds a lot of complexity, for dubious benefit: not having >> to start PHP code files with "<?php". > > Question - what is the performance hit of scanning the file for <?php and, if none are > found, restarting the parse process in code mode? > > If the hit isn't significant, this might be a way forward. There is the BC break that > files fed through the parser with nothing to parse will start creating errors, but that situation (a > php file with no <?php at all) feels like an error state anyway. As most projects use dynamic autoloading you'd have to add a stat call for a second filename, to try both .php and .phpc files. The performance hit for that is much bigger than any minuscule gain.