Le lun. 1 sept. 2014 à 20:13, Andrea Faulds a écrit :
>
> On 1 Sep 2014, at 17:29, Chris Wright wrote:
>
> > It's also worth noting that the "return NULL on zpp failure"
> > convention is not followed to the letter, I have seen places that
> > RETURN_FALSE - I can't remember exactly where I have
On 1 Sep 2014, at 17:29, Chris Wright wrote:
> It's also worth noting that the "return NULL on zpp failure"
> convention is not followed to the letter, I have seen places that
> RETURN_FALSE - I can't remember exactly where I have seen this but I
> will dig a ref out if anyone wants it.
Good po
On 1 September 2014 17:18, Andrea Faulds wrote:
>
> On 1 Sep 2014, at 04:56, Xinchen Hui wrote:
>
>> On Mon, Sep 1, 2014 at 6:01 AM, Andrea Faulds wrote:
>>> Good evening,
>>>
>>> Here’s a suggestion: Why don’t we make zend_parse_parameters emit
>>
>> ""Why not" is usually not a very good reason
On 1 Sep 2014, at 04:56, Xinchen Hui wrote:
> On Mon, Sep 1, 2014 at 6:01 AM, Andrea Faulds wrote:
>> Good evening,
>>
>> Here’s a suggestion: Why don’t we make zend_parse_parameters emit
>
> ""Why not" is usually not a very good reason for a change in the language
> syntax. " — Stas
The rea
On Mon, Sep 1, 2014 at 6:01 AM, Andrea Faulds wrote:
> Good evening,
>
> Here’s a suggestion: Why don’t we make zend_parse_parameters emit
""Why not" is usually not a very good reason for a change in the language
syntax. " -- Stas
> E_RECOVERABLE_ERROR on failure, rather than just emitting E_WAR
Good evening,
Here’s a suggestion: Why don’t we make zend_parse_parameters emit
E_RECOVERABLE_ERROR on failure, rather than just emitting E_WARNING and
returning FAILURE (causing the caller to typically bail out and return NULL)?
This would bring it into line with userland type hints, which also c
