Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at 
http://www.php.net/downloads.php

Please do not waste our time by asking for features which have already been implemented.

http://wiki.php.net/rfc/const_scalar_exprs

For a more detailed answer:

>Currently it's not possible to use any constants, variables or anonymous functions in a function parameter as default value. This is for example not possible:

>function saveUser($name, $surname, $company = CONSTANT_COMPANY_VALUE) {}

Did you actually test that code sample and check the manual to make sure your assertion was correct‽

You have been able to use constants as default values since PHP 5.3, and that came out 6 years ago. That function you provided? It already works.

Plus, since PHP 5.6, constant expressions are supported:

    function foobar($x = "hello, " . [1, 2, 3][SOME_CONST] / 3 ** 7);

It's true that you can't use variables, but that can be easily done in the body of the function.

Cool, my intention was definitely not to waste your time. I'm just not on 5.6 yet and I still don't see how the variables part is irrelevant, as it's not implemented and still stands as a feature request.

So now I wasted my time to request something that you just close the request for with an irritated comment. Thought a little bit more of you guys, but looks like it's just like with PHP - when you don't like something, you just throw an exception and send us to hell. Nice...

Sorry for the grumpy response ;) As Andrea already mentioned herself, this isn't yet implemented in the way that was requested, so closing as duplicate of existing https://bugs.php.net/bug.php?id=60544 instead. In there is a link to an SO thread with some more thoughts on the topic, might be of interest.

I don't think the request to support any expression is unreasonable per se - this would only cause issues with Reflection, but doesn't have any semantic issues like allowing arbitrary expressions for property initializers etc.

There's a number of relatively common non-constant parameter defaults, e.g. I've often seen parameters declared as `Foo $param = null` with a `$param = $param ?: new DefaultFoo` line in the body (whether this is good code design is another question).

Oh yeah, I apologise for being rather hostile before... It is a valid request, I was just surprised to see the first sample given we've supported it for a very, very long time.

Thanks for the clarification and pointing me to a right direction. I too apologise for a little over-reacting with my last comment, I was only genuinely surprised when I saw the first reply.

Also, sorry about the constant thing, I've probably not tried that for 6 years. And now that the variable thing re-appeared in my mind, I guess I just wanted to prove a point with a wrong example.

Best of luck, guys :)

Not for nothin', but HHVM supports any arbitrary expression in the default, even function calls.

function foo($bar, $baz = getBaz($bar)) { ... }