> > * All SAPIs will consider a "normal PHP file" as default input, could > > it be CLI, mod_php for Apache, or anything else (even FrankenPHP) > > Agreed, and nothing in the proposal changes that. Existing .php files behave > exactly as today through every SAPI. The proposal is additive: a new file > type that the engine handles differently, with zero impact on the existing > default path.
This is not entirely true, as the handling of `*phpc` (or whatever extension you are going to choose) _will_ change. People could already be using files with that extension. The BC impact is non-zero, though problems are arguably unlikely.
