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
On Mon, Feb 9, 2009 at 8:46 AM, Andrew Williams
wrote:
> 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
>
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
3 matches
Mail list logo
