Zeev,
>> Zeev, allow me to understand how this goes. Bob's discussions on the RFC
>> started 2 days ago. Based on the current rules, the RFC can only go to
>> vote
>> after 2 weeks. That means in 12 days starting now.
>>
>> So we are either violating the RFC rules by pushing the vote tomorrow or
>> we're delaying PHP7 for another 2 weeks maybe yet another TH RFC passes?
>
> Bob's RFC is effectively Andrea's v0.1 RFC which was discussed in detail and
> introduced well over two weeks ago.
> I hope we're not going to go into more and more extremes of playing a law
> firm and not an OS project.
We have minimum discussion periods for a reason. To allow people the
time to review proposals as much as to discuss them.
On the surface, yes, this looks like Andrea's 0.1 RFC. However, after
looking at it, it's definitely different. There's a very significant
behavior difference between the two:
Andrea's RFC had the following wording:
> The only exception to this is the handling of NULL: in order to be consistent
> with our existing type hints for classes, callables and arrays, NULL is not
> accepted by default, unless the parameter is explicitly given a default value
> of NULL. This would work well with the draft Declaring Nullable Types RFC.
This proposal has a different behavior here. It explicitly allows
nulls for types:
function foo(int $abc) { var_dump($abc); }
Unlike my proposal and any of Andrea's, calling foo(null) will be
int(0) instead of an error.
This is an important distinction as it basically undermines any
attempt at a nullable RFC, since it makes primitives implicitly
nullable.
So it's not effectively the original proposal. It does differ in a
very significant detail. This is why we have mandatory discussion
periods. Not for "playing law firm" but for being fair to each other.
Anthony.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
