comment on

I can't recommend some of this advice; it looks prone to making messes.

package dog;

Lowercase module names are, by convention, pragmas.

return(bless(dog->new(),$class));

Why double bless? If the parent constructor is at all sane, it allows subclassing.

my $doggie = new cockerSpaniel();

The indirect method invocation syntax is fraught with peril; it's ambiguous to parse and Perl occasionally guesses incorrectly depending on the compilation order of your code.

Also inheritance is not an essential part of object orientation. Arguably neither is encapsulation.

You're absolutely right about object design being important. Most tutorials never teach that, and it's vital to writing effective OO.

In reply to Re^2: kind of effort required for learning OO perl ?! by chromatic
in thread kind of effort required for learning OO perl ?! by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks