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

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
"not perl" is very much a gray area.

As an example, consider my Re: stdout/err redirection, my recent post. It indirectly suggests that a perl wrapper may not be the best solution to do redirection. It is about a tool that I feel a good complement to perl: socat. So does this node should be removed because it is "not perl"? I posted it because I consider it of genuine value even in the perlmonks forum. Nevertheless, as a form of politness, I state clearly from the start that this is not a perl solution so people have information to skip my post if uninterested.

-- stefp -- check out TeXmacs wiki


In reply to Re: Re: On Responsible Considerations by stefp
in thread On Responsible Considerations by footpad

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.