Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
With some editing and clarifications from feedback here and elsewhere in the thread, it will probably be something I'm happy to either link to in the Class::InsideOut documentation or possibly even add as Class::InsideOut::Tutorial.

In Class::InsideOut::Manual::About, it says,

All other implementation details, including constructors, initializers and class inheritance management are left to the user

This suggests to me that maybe a Class::InsideOut::Manual::BestPractices would be helpful. After all, most prospective users of C::IO are probably familiar with using classic hashref-based classes, and it's easy to just stick with what you know ... unless there's there's some easy-to-follow guidelines that say, ``Look, if you just need to write some simple classes with some inheritance, your best bet might be to use modules X, Y, Z, and do it like so.''.

By the way, for double-word score, include some references to relevant chapters and sections in Damian's PBP (detailing where C::IO BP differ from PBP being the most important, IMO).

IMO, a doc like that would make it a no-brainer to start off your InsideOut-OOP life with C::IO.


In reply to Re^2: RFR: Inside-out classes - a Class::InsideOut primer by j3
in thread RFR: Inside-out classes - a Class::InsideOut primer by radiantmatrix

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



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (4)
As of 2024-04-23 07:33 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found