PHP Class sharing?

[jamesmpollard]

Hi Guy's

 

Now this may be a stupid question but I was wondering if anyone could help me accomplish something. Here's what I'm trying to do (in brief).

 

CLASSONE.PHP

 

class one extends Core {
 
public function __construct() {
 
}
 
public function atestone() {
return $this;
}
 
public function __destruct() {
 
}
}

 

CLASSTWO.PHP

 

class two extends Core {
 
public function __construct() {
 
}
 
public function atesttwo() {
return $this;
}
 
public function __destruct() {
 
}
}

 

CORE.PHP

 

class Core{
 
public function __construct() {
 
}
 
public function testcore() {
return $this->atestone();
// OR
return $this->atesttwo();
}
 
public function __destruct() {
 
}
}

 

I'm looking to have a core class basically. Ideally, all classes can utilise other functions but my main aim is to have one core class that can use (freely) all other classes that are extended to it.

 

Is this possible?

 

Thanks in advance

 

James

[ginerjm]

The reason to have a class that extends another class is to add some functionality to the parent class ie, the first class. Your goal of having a class called 'core' that will use all the classes extended from it is IMHO a bit backwards. Yes the 'core' class can be used by all your scripts but the functionality of the child classes that extend it will not be available unless you include them and construct objects of each child class. Then those items will have all the functionality of the specific class they belong to as well as the 'core' class.

[jamesmpollard]

The reason to have a class that extends another class is to add some functionality to the parent class ie, the first class. Your goal of having a class called 'core' that will use all the classes extended from it is IMHO a bit backwards. Yes the 'core' class can be used by all your scripts but the functionality of the child classes that extend it will not be available unless you include them and construct objects of each child class. Then those items will have all the functionality of the specific class they belong to as well as the 'core' class.

 

Sorry, I didn't really explain too well.

 

I will be having a bootstrapper file that will include all the classes (class one, class two and so on) and the core. I would then like to use the core to use all other classes. To make life easier, simpler and to have less clutter, ect.

[jamesmpollard]

Maybe a better question would be, what is the best way of using classes in a simple, easy, OOP manner? Bare in mind that many of my classes need to use functions from other classes to save cloning the same functions many times over.

 

Interfaces, abstracts, ect. I'm not fussed, just need as simple way of doing it.

 

EDIT: Forgot to mention, by OOP, I need the classes to be "chained". That would probably solve the problem of using functions from separate classes.

Edited June 6, 2015 by jamesmpollard

[jcbones]

Dependency Injection is the terms you are looking for.

class what {
 function __construct(ever $ever) {
  $this->ever = $ever;
 }
 
 public function DIme() {
 return $this->ever->me();
 }
}
 
class ever {
 public function me() {
 return 'Method in class ever.';
 }
}
 
$ever = new ever();
$what = new what($ever);
echo $what->DIme();

Edited June 6, 2015 by jcbones

[ignace]

There is no reason you should have one class that does and knows everything. It's far better to create specialised classes for your pages. It's also far better for performance as you'll quickly be loading too many unneeded classes.

[jamesmpollard]

 

Dependency Injection is the terms you are looking for.

class what {
 function __construct(ever $ever) {
  $this->ever = $ever;
 }
 
 public function DIme() {
 return $this->ever->me();
 }
}
 
class ever {
 public function me() {
 return 'Method in class ever.';
 }
}
 
$ever = new ever();
$what = new what($ever);
echo $what->DIme();

Is there a way of making it so that the classes are not all in one file?

[jamesmpollard]

There is no reason you should have one class that does and knows everything. It's far better to create specialised classes for your pages. It's also far better for performance as you'll quickly be loading too many unneeded classes.

Agreed. A crazy man would make one giant class for the whole site, benchmarking would be a disappointing result lol.

[jcbones]

Of course you don't have to put all classes in one file.  That is what include is for.

[ginerjm]

As long as you realize that if 'core' is your master class and 'one' and 'two' are classes that extend 'core', you can't use just 'core' and access the methods that classes 'one' or 'two' define. You made it sound like that in your reply to my post.