Daniel Schierbeck wrote:
Stefan wrote:
It's a bug.
* Siehe http://bugs.php.net/bug.php?id=28444 ... und ...
* http://news.php.net/php.bugs/63652
A workaround is possible using __call( $name, $args) { return(
$this-__get( $name)); }. But it sucks, since constructs using array
Frzzman wrote:
Daniel Schierbeck wrote:
Stefan wrote:
It's a bug.
* Siehe http://bugs.php.net/bug.php?id=28444 ... und ...
* http://news.php.net/php.bugs/63652
A workaround is possible using __call( $name, $args) { return(
$this-__get( $name)); }. But it sucks, since constructs
Do you guys have any idea why this code:
?php
class Foo
{
private $elem = array();
public function __get ($prop)
{
if (isset($this-elem[$prop])) {
return
It's a bug.
* Siehe http://bugs.php.net/bug.php?id=28444 ... und ...
* http://news.php.net/php.bugs/63652
A workaround is possible using __call( $name, $args) { return(
$this-__get( $name)); }. But it sucks, since constructs using array
indices are impossible as
Stefan wrote:
It's a bug.
* Siehe http://bugs.php.net/bug.php?id=28444 ... und ...
* http://news.php.net/php.bugs/63652
A workaround is possible using __call( $name, $args) { return(
$this-__get( $name)); }. But it sucks, since constructs using array
indices are impossible as
5 matches
Mail list logo