On 29/10/2019 21:56, Mike Schinkel wrote:
It would be much better to keep it separate, and opt into it via a
declare() statement, or a package configuration, or a file extension.
There have been proposals for a single flag, lots of separate flags,
a complete "P++" dialect, or bundles of settings ("Editions").
Correct me if I am wrong, but all of those have been objected to,
strenuously, by at least several people on the list.
Indeed, but adding "the strict mode will be faster than the legacy mode"
is likely to make those objections stronger, not resolve them, unless
you can demonstrate _why_ the strict mode needs to be mandatory for the
pre-compiled mode.
Both/all modes should get the same performance improvements, except
where the actual features are necessarily slower or faster.
Fine. But a pre-compiler still could have merit.
Absolutely! In case you've forgotten, it was my remark that started this
whole discussion: https://externals.io/message/106844#107656
One of the things I would like to see from a pre-compiler is
getting rid of the need to deal with an autoloader and hence we
able to store multiple related classes in the same file.
Yes, I think moving from auto-loading to eager loading would make sense
for a lot of projects.
Regards,
--
Rowan Tommins (né Collins)
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
