I guess many people just prefer the OO interface. It is more neat and tidy?There are neat and tidy OO interfaces. There are neat and tidy non-OO interfaces. There are far more messy interfaces, both OO and non-OO. Whether an interface is "neat and tidy" has less to do with OO vs non-OO than with the quality of the programmer. Of course, "neat and tidy" is something very subjective. What you find "neat and tidy", I may find an incredible mess.
IMO, it entirely depends on the problem whether an OO-interface is "better" (for some definition of "better") than a procedurial interface is. And for many problems, it hardly matters.
I find it far more easy to write spaghetti code/interface/documentation using OO than using procedures.
In reply to Re: Cpan module interface: OO or just a module?
by JavaFan
in thread Cpan module interface: OO or just a module?
by theantler
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |