[RESOLVED] new Anything()->aMethod()

Verdagon

My bad, thanks nrg, it was a retyping error.

echo new DateTime()->getOffset();

still produces PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ',' or ';'

It still gives me an error. Any idea how to get around this?

nrg_alpha

Hmm.. what does your class look like (code wise?). Seems like perhaps you are missing a semi-colon on a line within your class somewhere?

Verdagon

Thanks for the fast replies. Here's my entire file:

<?php
	echo new DateTime()->getOffset();
?>

And here's my entire error:
[25-Jan-2009 03:52:24] PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ',' or ';' in /Users/Verdagon/Desktop/perello/server/mydate.php on line 2

nrg_alpha

I was refering to the code inside your class DateTime()

nrg_alpha

Come to think of it, when I run this script, I get the same resulting error, which leads me to think you cannot echo like that:

class Bear { 
    // define properties 
    public $name; 
    public $weight; 
    public $age; 
    public $sex; 
    public $colour; 

// define methods 
public function eat() { 
    echo $this->name." is eating... "; 
} 

public function run() { 
    echo $this->name." is running... "; 
} 

public function kill() { 
    echo $this->name." is killing prey... "; 
} 

public function sleep() { 
    echo $this->name." is sleeping... "; 
} 
}

echo new bear->sleep();

class taken from Zend....
But I'm more curious as to why you cannot get:

$d = new DateTime();
echo $d->getOffset();

Verdagon

DateTime is a standard php class. http://us3.php.net/manual/en/class.datetime.php

It doesnt matter that I'm using DateTime or any other class, this syntax still gives me errors. I was just wondering if anyone else has ever run into this...

Verdagon

With your code I get this error: PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ',' or ';' in /Users/Verdagon/Desktop/perello/server/date.php on line 26

nrg_alpha

Verdagon;10900535 wrote:
DateTime is a standard php class

Oh, the default built in one.. yeah, I keep forgetting about that one..

When I simply do this, I get a result:

$d = new dateTime();
echo $d->getOffset();

So I'm wonder aloud if this is PHP version dependant? Are you using a fairly modern version?

nrg_alpha

Verdagon;10900536 wrote:
With your code I get this error: PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR, expecting ',' or ';' in /Users/Verdagon/Desktop/perello/server/date.php on line 26

Yeah, that was my point.. so when I try:

echo new dateTime()->getOffset();

I get the same problem as you.. but as I just mentioned, I do get results with:

$d = new dateTime();
echo $d->getOffset();

EDIT - So I am guessing you cannot echo out a new class without creating an object first (I've never tried it before coming across this thread). But it doesn't explain why you cannot create an object and echo it out that way..

Verdagon

A mystery, isn't it? But it's bigger than that. It's not just echo that won't do this, its anything. Just writing this gives me an error:

<?php
	new bear->sleep();
?>

PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /Users/Verdagon/Desktop/perello/server/date.php on line 2

In java, we can write new Bear().sleep() and it will work just fine. I wonder why PHP can't do that? I run into this all the time in my php code... I don't like making unnecessary variables, y'know?

Piranha

It is possible that PHP evaluates dateTime()->getOffset() before it evaluates new.

I don't have PHP installed, making it hard to test. But if that is the case this should work, forcing PHP to create a new object first:

echo (new dateTime())->getOffset();

nrg_alpha

I think you need to create an object first, as in your $d=new dataTime()...
I don't think you can simply echo out a class in itself as we have been trying (again.. I never even thought of trying that until this thread).. so I am more concerned with why, even when you create an object ($d) and try and echo out the results from the $d->getOffset(); it doesn't work for you.

This is why I am asking which version of PHP is your server using (it might not be an issue.. I don't know.. Im not sure how old this default dateTime class is with regards to PHP versions)..

As for Java, well, PHP isn't quite Java..

nrg_alpha

Piranha;10900542 wrote:
It is possible that PHP evaluates dateTime()->getOffset() before it evaluates new.

I don't have PHP installed, making it hard to test. But if that is the case this should work, forcing PHP to create a new object first:
echo (new dateTime())->getOffset(); 

I tried your suggestion, Piranha.. same error I'm afraid.

Verdagon

Oh no, I must have been unclear.

$d = new DateTime();
echo $d->getOffset();

this DOES work. I was merely wondering why php will run that but won't run it when it's all in one line such as new DateTime()->getOffset()

I tried what you suggested, Piranha, but no luck. It gives the same error.

nrg_alpha

Verdagon;10900545 wrote:
Oh no, I must have been unclear.
$d = new DateTime();
echo $d->getOffset();
this DOES work. I was merely wondering why php will run that but won't run it when it's all in one line such as new DateTime()->getOffset()

Ooooohhhhh hehe... My bad.. I misunderstood..well then, that solves everything 😉
I guess you cannot echo out a class in itself...

Weedpacket

nrg_alpha's post above has it right: new Anything()->aMethod() is just plain bad syntax.

Verdagon

Well, I'd say it's bad syntax according to the current PHP, but maybe it's something that should be changed in future PHPs?

I mean, new DateTime()->getOffset() makes perfect sense to me...

NogDog

I believe it is because new returns an actual object, not a reference to an object. Method chaining only works with references (which is the default mode in PHP5 for copying existing objects). Whether something should be changed to allow what you want to do is a theoretical question for which I have no idea what should or should not be the "correct" answer in terms of OOP theory.

nrg_alpha

Sounds like something worthy of a blog article...

laserlight

NogDog wrote:
I believe it is because new returns an actual object, not a reference to an object.

I do not think so. As of PHP 5 new returns a reference (as in pointer) to the newly created object.