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
> On Oct 29, 2019, at 5:49 PM, Rowan Tommins wrote:
>
> I think the problem is that as soon as you have two engines targeting
> different feature sets, it will be hard to persuade people to spend equal
> attention on both. If all the new features end up being added to one engine,
> the other
On 29/10/2019 19:04, Mike Schinkel wrote:
Note that this was exactly what "P++" was intended to avoid - the two
dialects would exist in the same engine, and get the same performance and
security enhancements.
It could also be one engine, it just seemed like that coupling
would be more
On 28-10-19 00:04, Rowan Tommins wrote:
> - a static analyser that can infer types in a PHP program; we know
> that's possible from a number of third-party tools, although they do
> rely on docblock comments for things the language doesn't (yet) let you
> define
Opcache already performs type
> On Oct 28, 2019, at 6:00 AM, Rowan Tommins wrote:
>
> Current tools tend to actually work on a directory level, because you don't
> actually know what namespaces are involved until after you've loaded it,
> and a file can include code for two completely separate namespaces. My
> thinking was
