Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

comment on

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

I personally believe that it's too bad that the quest is over. Especially because I did dare to suggest some ideas of mine, but only in reply to other comments. (I presume I should just blame myself for being so slow...) So, however moot it may seem, here I am with my "main" post-mortem suggestion - perhaps it may turn out useful for some future project: there have been a YAPE and a JAPE. But then, how about simply APE? (Three letters names are the best ones, IMHO!) For: "A Perl Editor." Or with the "A" standing for "Another." Or again, the one I like most - in a recursive fashion: "Ape: Perl Editor."

If you can't understand the incipit, then please check the IPB Campaign.

In reply to Re: Name a Perl IDE - get a Perl book or YAPC ticket by blazar
in thread Name a Perl IDE - get a Perl book or YAPC ticket by szabgab

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.