Class problem...

[moon 111]

I have a class User which when created as an object gets the information for a specific user and has functions that the user could use (change email, add credits etc.). I now would like to add some functions for adding, deleting and managing users, and I'm not sure if I should create a new class or put it in the old one.

 

Thanks

[KevinM1]

I have a class User which when created as an object gets the information for a specific user and has functions that the user could use (change email, add credits etc.). I now would like to add some functions for adding, deleting and managing users, and I'm not sure if I should create a new class or put it in the old one.

 

Thanks

 

There are really two questions you have to ask:

 

1. Should all users be allowed to have those administration capabilities (which I put in bold) available to them from the outset?

2. Does it make sense to put functions that make sweeping system changes into the same class that previously allowed only individual changes?

 

I can't think of a reason, other than wanting to save a few keystrokes, to shoehorn administration functions into a generic user class.  This sort of thing is better left to an administration class of some sort that is responsible for largescale user manipulation.

[nloding]

I did it this way:  Make an Admin class that does admin functions.  If $user->is_admin (or however you check), instantiate the $admin class.  It is only instantiated on admin panel screens for 'better' security.

 

If there's a better way, let me know.  I'm still wrapping my head around OOP.