Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
For what it's worth, I was quite active in these parts in the early naughts, after which I went on hiatus for a few years. Recently I've been poking around the halls again.

In my case, there was no particular reason, just changes in life, work, interests. More recently I had to become proficient in p-p-p...p-p-p...Python! (don't tell anyone) Naturally I spent less time with perl during that.

Even more recently, I started dabbling around with some XS extensions and perl, plus have begun experimenting with perl6. Messing about with perl again naturally led me to wonder what the monks have been up to, so here I am.

Things do seem slower, though. Personally I think EV2 is showing its age in this 2.0 world.


In reply to Re^2: Perlmonks Threaded Article Viewer (Trend) by mojotoad
in thread Perlmonks Threaded Article Viewer by jcwren

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.