I definitely hate having to test the return value and then getting the
error message via a function call. +1 for ability to throw exceptions
instead.
On 10/09/17 02:24, Andrea Faulds wrote:
Hi everyone,
Craig Duncan previously sparked discussion here about JSON's
error-handling behaviour. U
has been asked before.
Any tips would be greatly appreciated.
Thank you!
Regards,
Ilija
--
--
*Bradley Weston [bweston.me]*
Telephone: 0845 004 0662
Mobile: +44 (0) 7902 672289
This message is intended only for the use of person(s) (\"the Intended
Recipient\") to whom it is
I agree, doing lots of if statements gets bloated. Someone would only
use this method if they was comfortable with it either returning null or
the desired result.
On 11/12/2014 16:00, Rowan Collins wrote:
guilhermebla...@gmail.com wrote on 11/12/2014 15:57:
Not trying to demerit the proposal,
Somehow HHVM has this working http://3v4l.org/5AFSA
On 20/11/2014 00:44, Stanislav Malyshev wrote:
Hi!
The point of this discussion is that there is an RFC on the table
which can be implemented in such a way that it fixes this behaviour
(by introducing a default parent, or injecting an empty
Opps I meant PHP 5.4.33
On 09/10/2014 12:17, Chris Wright wrote:
On 9 October 2014 10:08, Bradley Weston wrote:
Reference to bug: https://bugs.php.net/bug.php?id=62596
PHP 5.3.33 - FPM not given getallheaders function.PHP 5.3.33 - FPM not given
getallheaders function.
While this does need
Reference to bug: https://bugs.php.net/bug.php?id=62596
PHP 5.3.33 - FPM not given getallheaders function.PHP 5.3.33 - FPM not given
getallheaders function.
PHP 5.4.33-1~dotdeb.1 (cli) (built: Sep 19 2014 12:11:25)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-201
