Though be aware that Eiffel not only is OO, it's also "design by contract". There's a strong focus on checking pre- and postconditions and invariants†.

There's nothing wrong with "design by contract", but it might bog you down if you're looking at Eiffel just to get more knowledgeable about OO.

†To explain in a few lines and with lots of handwaving: each class has a set of invariants defined. Each time you call a method in an object of said class, the invariants are checked upon method exit. Exception on failure. Loop invariants and postconditions are checked in a similar way.

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.