php4 oop theory

[g0dzuki]

I've been trying to wrap my head around OOP for the last several hours but i'm having a hard time breaking my self of old coding habbits. :o

So here's my question... I guess I just want to make sure I understand this correctly. I create a class and in this class would be all my functions and variables that have to do with that class.

So for example, a user authentication system would be something like:

<?php

class user_authentication {

   // Class Variables
   var $username
   var $email

   // Create User Account
   function create_account() {
          // Some Code
   }

   function validate_username() {
          // Some Code
   }

   function validate_password() {
          // Some Code
   }

   function validate_email() {
          // Some Code
   }

}

?>

... and so on.

Would it be better to create one class that does the account regitration (password check, email validation, etc) and another that does the actuall authentication (loggin in, etc)? All in the same class?

I guess I'm just looking for any tips on how to go about designing an OOP based app. I've read a lot of the other threads on the board, and I think i'm on the right track but would like to see what the gurus think...

Thanks!

[pyro3k]

it looks like you got the right idea. id personally do it all in the same class.

if you really want to get into OOP try using php5 instead. its much better for OOP as it has static members, private and public methods and constuctors and destructors.

OOP in php4 is a little awkward and unnatural.

[dream_scape]

classes really should be discrete and focused. The only time I really stray some from this is with utility classes, like string utilities.

Let me ask you, what does creating an account have to do with authenticating a user's login?

I'm no entirely sure what you mean by validate_email, but if you mean like validate it is in a valid format, what does that have to do with authenticating a login either?