Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
You've seen Preface (PERl REFACtoring Engine) then? I still can't quite believe that I got the Extract Method refactoring working. The way it works is utterly evil, but it is possible (and, AFAICT from the spike I did) should work in many cases.

Detecting the lexical variables involved in a code segment by repeatedly evaling and modifying the same section of code based on $@ until compiles successfully is, frankly, weird. Especially when, to get things to be compiled in the right context you had to do some magic with coderefs in @INC.

Once I've got Pixie good and stable, I really should go and revisit Preface...

In reply to Re:^N Self-improvement and TMTOWTDI by pdcawley
in thread Self-improvement and TMTOWTDI by Tanalis

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.