://paste.roguecoders.com/p/16e1e953e8b1890bcaaba00eb8408dd7.txt
If someone with the appropriate karma could review this and commit it
to trunk, that would be grand.
Thanks,
Joël.
On Fri, Jul 16, 2010 at 5:52 AM, Richard Quadling rquadl...@gmail.com wrote:
On 16 July 2010 02:42, Joel Perras joel.per...@gmail.com wrote
What's confusing about it? Each expression means something very
different and distinct.
I use $foo(), new $foo(), classname::$foo, classname::$foo(),
$bar::$foo, $bar::$foo(), etc. on a regular basis, and it can make for
some very elegant, concise and readable code.
Moreover, this really isn't
array_combine(array(), array()) triggers an E_WARNING and returns
false, instead of simply returning an empty array with no triggered
warning.
This is not a bug, but was intentionally written as such - see
ext/standard/array.c around lines 4480-4483 in the 5.3 branch in the
current svn HEAD:
I'll second that. I'm quite surprised that it was such a clean
addition to the parser. I owe you a few beers, Felipe.
-Joël
On Mon, Jun 7, 2010 at 9:16 PM, Jonathan Wage jonw...@gmail.com wrote:
Thanks a bunch. This is a very nice improvement to PHP!
- Jon
On Mon, Jun 7, 2010 at 12:58 PM,
+1 for option #2.
Joël.
On Sun, Apr 18, 2010 at 11:58 PM, Adam Harvey ahar...@php.net wrote:
As at least some of you would already be aware, there's a
long-standing issue with using PHP in a Turkish or Azeri locale,
namely that case-insensitive lookups within the Zend engine (method
names,
