Concatenating object methods

[crater]

I'm using PHP 5.2.

I've created classes to embody HTML elements for a particular project
I'm currently working on.

All setter methods in the classes return $this so that I can string
the
methods together in an attempt to reduce "page bloat".

// create a text link
$link1 = new htmlElement("a");
$link1->addAttribute("href", "http://homepages.nildram.co.uk/
~iccarter")
->addAttribute("target","_blank")->addAttribute("name",
"htmlElement1");
echo $link1->addContent("My personal web site")."<br><br>\n";
 

My anchor element is duly output exactly as expected.

A question naturally arises from this. Is there a way to do the
following?...

$link1 = new htmlElement("a")->setAttribute("name", "value");
 
or
 
($link1 = new htmlElement("a"))->setAttribute("name", "value");
 

It's not an issue. I'm just curious.

[Tom]

On Jan 31, 11:45 am, "crater" <[e-mail]:

I'm using PHP 5.2.

I've created classes to embody HTML elements for a particular project
I'm currently working on.

All setter methods in the classes return $this so that I can string
the
methods together in an attempt to reduce "page bloat".

// create a text link
$link1 = new htmlElement("a");
$link1->addAttribute("href", "http://homepages.nildram.co.uk/
~iccarter")
      ->addAttribute("target","_blank")->addAttribute("name",
"htmlElement1");
echo $link1->addContent("My personal web site")."<br><br>\n";
 

My anchor element is duly output exactly as expected.

A question naturally arises from this. Is there a way to do the
following?...

$link1 = new htmlElement("a")->setAttribute("name", "value");

                  or

($link1 = new htmlElement("a"))->setAttribute("name", "value");
 

It's not an issue. I'm just curious.

This probably won't work but you could try returning $this in your
constructor:

[ in your class definition: ]
function __construct( $element ) {
// some code
return $this ;
}

This isn't the best programming though... a better way to get the
results you need would be to make constructor parameters optional, so
you can pass what you need to when you're creating a new instance of
this class, e.g.:

function __construct( $element, $name = "", $value = "" ) {
if ( $name && $value ) {
$this->setAttribute($name, $value) ;
}
}

I realize stringing together methods might be good now for a clean
looking page, but if you need to modify your code down the line (or
worse another programmer needs to take over the project), this will
probably cause more problems than it solves. Just a suggestion!

[Michael Fesser]

..oO(crater)

>A question naturally arises from this. Is there a way to do the
following?...

$link1 = new htmlElement("a")->setAttribute("name", "value");

                 or

($link1 = new htmlElement("a"))->setAttribute("name", "value");

It's not an issue. I'm just curious.

Nope. PHP's syntax doesn't allow that. You could write a function that
creates and returns the new object, something like

$link = createHtmlElement('a')->setAttribute(...);

Micha

[bob.chatman]

On Jan 31, 8:45 am, "crater" <[e-mail]:

I'm using PHP 5.2.

I've created classes to embody HTML elements for a particular project
I'm currently working on.

All setter methods in the classes return $this so that I can string
the
methods together in an attempt to reduce "page bloat".

// create a text link
$link1 = new htmlElement("a");
$link1->addAttribute("href", "http://homepages.nildram.co.uk/
~iccarter")
      ->addAttribute("target","_blank")->addAttribute("name",
"htmlElement1");
echo $link1->addContent("My personal web site")."<br><br>\n";
 

My anchor element is duly output exactly as expected.

A question naturally arises from this. Is there a way to do the
following?...

$link1 = new htmlElement("a")->setAttribute("name", "value");

                  or

($link1 = new htmlElement("a"))->setAttribute("name", "value");
 

It's not an issue. I'm just curious.

Why dont you just do this:

$link1 = new htmlElement("a");
$link1->setAttribute("name", "value");

If nothing else your idea will lead to confusion when you come back to
it later in life.

The rule i have always tried to follow (except in perl) is ...
One statement
One line