Jump to content

Skeleton Class


berridgeab

Recommended Posts

Hi

 

Just fishing for opinions here, is it a good idea to break classes down to skeleton parts?

 

i.e.

 

I have a class called Person.

 

class Person
{
   public $id;
   public $name;
   public $age;

   //Getters / Setters Go here
   function id() { return $this->id; }

   function load($id)
   {
      //Database loading logic here
   }
}

 

To something more reuseable i.e.

 

abrstract class SkeletonPerson
{
   public $id;
   public $name;
   public $age;

   //Getters / Setters Go here
   function id() { return $this->id; }
}

class Person extends SkeletonPerson
{
   function load($id)
   {
      //Database loading logic here
   }
}

Link to comment
Share on other sites

Yes it's a good idea to abstract as much functionality away you can into base classes. Just be aware though that php is only single inheritance, this means you can end up with long chains of relationships.

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.