Re: Re: com php-src: Bug 49898 __getCookies() method implementation: ext/soap/soap.c ext/soap/tests/bug49898.phpt
| From: | Pierre Joye | Date: | Thu, 19 Jun 2014 18:22:58 +0000 |
| Subject: | Re: Re: com php-src: Bug 49898 __getCookies() method implementation: ext/soap/soap.c ext/soap/tests/bug49898.phpt | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74999@lists.php.net to get a copy of this message | ||
On Jun 19, 2014 5:17 PM, "Rowan Collins" <rowan.collins@gmail.com> wrote:
>
> Ferenc Kovacs wrote (on 19/06/2014):
>
>> Personally I think that 1 would be acceptable if we can keep these
feature
>> introductions as rare events, 2 would be a somewhat arbitrary
restriction,
>> and 3 could be confusing for the early adopters(slow adopters wouldn't
>> really realize that the 5.6.X version missing feature Z was released
after
>> 5.5.Y which has the feature, so they wouldn't have expectations),
>
>
> Is there a convention in the manual for the situation where a function is
introduced in parallel in different branches? It can't say "PHP 5 >=
5.5.15" if it's not also in 5.6.0. But if we were confident of it being in
5.6.1, it could say "PHP 5.5 >= 5.5.15 < 5.6, >= 5.6.1" or something less
messy than that, and anyone using 5.6 would know that it was coming to them
soon...
Reading this post tells me exactlt why new features should go in x.y+1. It
is a pain to figure which point versions introduced which features. Always
was.