[SOLVED] How do some programmers do this...

[Demonic]

I don't know what its called but the Objects look like so:

 

$var->var->var();

 

How does that work?

[teng84]

actually its a class thin

 

when you say $db->connect();

 

it means that the class db is calling the function connect in the class

[Demonic]

Naw not like that.

 

$var->var->var();

 

 

I seen some IPB source and it does some stuff like that.

 

Not $var->var();  I already know how classes work I want to know how the above object works though.  Its unique more advanced.

[hitman6003]

It's calling the function "var()" inside of the object "var" which was created inside of the object "var"

[Demonic]

Can you show me an example of how I would do that?

[hitman6003]

<?php

class foo {
public var $bar;

protected function __construct () {
	$this->bar = new bar();
}
}

class bar {
public function foo_bar() {
	return "FUBAR (F'd Up Beyond All Repair)";
}
}

$blah = new $foo;

echo $blah->bar->foo_bar();

?>

[teng84]

hitman I always wonder why you guys use public in the class isnt class is made to act as public????

then y???

[Demonic]

PHP 5 stuff, it wont work correctly with PHP 4.

 

How would I do this just using PHP 4?

 

I got an error with your example:

 

Parse error: syntax error, unexpected T_VAR, expecting T_VARIABLE in C:\SERVER\www\foobar.php on line 4

 

 

I'm using WAMP 5 PHP 5.2.3

[hitman6003]

I suppose that it isn't necessary to declare a function public, since according to the manual a method without a declaration is automatically public (http://us2.php.net/manual/en/language.oop5.visibility.php#language.oop5.visiblity-methods).

 

I do it mostly for consistency, and also because I suppose that I'm slightly OCD.

 

Remove the public / protected from the vars and methods, and change the function named "__construnct" to the name "foo".

[teng84]

although we both know that its not necessary its being stated by PHP.net so i guess ill go with you even if it doesnt make any difference

[Demonic]

I suppose that it isn't necessary to declare a function public, since according to the manual a method without a declaration is automatically public (http://us2.php.net/manual/en/language.oop5.visibility.php#language.oop5.visiblity-methods).

 

I do it mostly for consistency, and also because I suppose that I'm slightly OCD.

 

Remove the public / protected from the vars and methods, and change the function named "__construnct" to the name "foo".

 

Ok cool it worked perfectly:

 

<?php

class foo {
var $bar;

function foo () {
	$this->bar = new bar();
}
}

class bar {
function foo_bar() {
	return "FUBAR (F'd Up Beyond All Repair)";
}
}

$blah = new foo;

echo $blah->bar->foo_bar();

?>

[btherl]

IMHO, specifying things which are the default anyway (such as public) is good practice.  It adds to the documentation, and ensures your code will run correctly even if the defaults change.  It also helps catch bugs, as you may not always be correct in what you assume the default to be.