Sorry for bringing an old thread back to life, but imo this needs some
more attention.
Sebastian wrote:
hi,
PHP6 still replaces . with an underscore in variables from outside. this
is an old behavior forced by register globals so i would say its a bug since
. is valid in array keys.
Původní zpráva
Předmět: Re:Namespace resolution rules has been changed?
Od: David Grudl [EMAIL PROTECTED]
Datum: 10.11.2008 23:53
Can you please point us to an example describing this best practice?
For example Namespace Naming Guidelines in .NET
Hello David,
On Tue, Nov 11, 2008 at 5:16 PM, David Grudl [EMAIL PROTECTED] wrote:
Hello *internals* and Marcus!
What do you think about possibility to implement to PHP 5.3 several useful
default exceptions?
(note that InvalidArgumentException, RuntimeException and LogicException
exists
On Nov 11, 2008, at 04:10 PM, Mark van der Velden wrote:
Sorry for bringing an old thread back to life, but imo this needs some
more attention.
Sebastian wrote:
hi,
PHP6 still replaces . with an underscore in variables from
outside. this
is an old behavior forced by register globals so i
Hi Mark
2008/11/11 Mark van der Velden [EMAIL PROTECTED]:
Sorry for bringing an old thread back to life, but imo this needs some
more attention.
Sebastian wrote:
hi,
PHP6 still replaces . with an underscore in variables from outside. this
is an old behavior forced by register globals so
Hi,
recent change in namespace code introduced new bug, please consider:
?php
namespace tests;
class t1 {
function abc(\stdClass $std = null) {
}
}
?
triggers Fatal error: Default value for parameters with a class type hint
can only be NULL
where the same w/o namespace definition
Hello *internals* and Marcus!
What do you think about possibility to implement to PHP 5.3 several
useful default exceptions?
(note that InvalidArgumentException, RuntimeException and LogicException
exists since PHP 5.1)
/**
* The exception that is thrown when the value of an argument is
*
I was pointed to the http://wiki.php.net/rfc site the other day at the
ATLPHP user group and found the traits and related RFC's.
I just read the RFC on grafts and traits for PHP. Great ideas! There
is one other thing I'd like you to take a look at as well though,
that's very useful.
I don't see it would work with something like
import_request_variables() unless thats removed or extract(), which is
some of the reasons for this replacement feature afair.
There was never a need for the replacement to occur for the GPC
superglobals.
If import_request_variables() needs it,
class Helloworld
{
public function sayHello() { print HELLO; }
}
category HelloworldExtras on Helloworld
{
public function sayWorld() { print World; }
}
$h = new Helloworld;
$h-sayWorld(); // print WORLD
This is extremely beneficial for lightweight extension of classes
without
On Wed, Nov 12, 2008 at 03:57, Stan Vassilev | FM [EMAIL PROTECTED] wrote:
I don't see it would work with something like
import_request_variables() unless thats removed or extract(), which is
some of the reasons for this replacement feature afair.
There was never a need for the replacement
Hannes Magnusson wrote:
On Wed, Nov 12, 2008 at 03:57, Stan Vassilev | FM [EMAIL PROTECTED] wrote:
I don't see it would work with something like
import_request_variables() unless thats removed or extract(), which is
some of the reasons for this replacement feature afair.
There was never a
On Tue, Nov 11, 2008 at 23:00, Etienne Kneuss [EMAIL PROTECTED] wrote:
Hello David,
On Tue, Nov 11, 2008 at 5:16 PM, David Grudl [EMAIL PROTECTED] wrote:
Hello *internals* and Marcus!
What do you think about possibility to implement to PHP 5.3 several useful
default exceptions?
(note that
13 matches
Mail list logo