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

- Thread: https://externals.io/message/131150
- Original archive: https://news-web.php.net/php.internals/131150
- Started by Casper Langemeijer on 2026-06-05T06:04:21+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #131150 — Casper Langemeijer — 2026-06-05T06:04:21+00:00

URL: https://externals.io/message/131150#131150

> > […]
> 
> 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.