Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

From Perl Design Patterns Book:


Because we don't know how programs will reinvent themselves, we don't know how to design an "Interface" *, what composite types are involved, and what containment and inheritance hierarchies will look like. In the beginning, we seldom know that a program will grow into this at all!

"Interface" is much more trendy than the ailing "Application Programmer Interface", or "API". Generally speaking, an interface is how you use something. Just like any consumer appliance, modules should be used in very specific ways: do not submerse in water. Do not use while driving. Do not paint over vents. Do not insert fingers. Do not leave on "high" setting unattended. Not only do programs use APIs to talk to the outside world, they use them internally to connect parts.

Perl's easy going attitude and powerful features shine here. After a program has devised a solution to a logic problem, and after it has proved its continued usefulness, we have a route for improvement.

Ciao, Valerio

Update: thank you all for the links, really interesting. It would be nice to see these links listed in tutorials.

Another quote, but from Dominus's site:

The "Design Patterns" solution is to turn the programmer into a fancy macro processor


In reply to Re: Perl Design Patterns Book by valdez
in thread Perl Design Patterns Book by rasta

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?

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

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2024-06-12 15:18 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.