Syntactic Confectionery Delight | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I've found this the best way to do it, mostly because it allows lots of generalising and lots of use of polymorphism. I have objects of class Person, Invoice, Business etc and they all basically want the same methods called on them. Using a class method Person->newIterator actually returns an instance of PersonIterator which is subclassed from DBIterator. PersonInterator, etc, instances are created on the fly and how they behave depends on the arguments passed by newIterator. Because all the Person, Business, etc classes are all subclassed from the same Entity class, the calling program doesn't actually have to know what class it is dealing with. So calling: $any_Iterator = $any_class->newInterator returns a an instance of something subclassed from DBIterator. Note DBIterator, itself, is abstract. Then you can keep calling: $any_Iterator->nextElement; until it returns undef. Is this a naughty use of symbolic refs? I don't know. But what I do know is that I find this code easy to maintain easy to extend and easy to tweak. In reply to Re: Re: OO Application Design
by Nomad
|
|