Re: Fwd: [PHP] Interface OOP

2009-02-09 Thread Jochem Maas
each class should focus on a single area of responsibility. therefore the login check doesn't belong in class A or B, instead it belongs in the code consuming the functionality of said classes. validate()) $bee->ExtractRawData(); ?> you could alternatively look into either extending the

Fwd: [PHP] Interface OOP

2009-02-09 Thread Andrew Williams
Hi, I am working on a back end OOP project with about about 18 classes of Object but some of the Objects shear one or two functions in common, like external login system . What is the best way to avoid a repeatable function among the classes without using global object instance. class a{ functio