Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I spent time addressing all these concerns in my post. I find it weird that you chose to disreguard them when suggesting an improvement.

Sorry. I cut&paste from one of my existing scripts (which didn't support them), and didn't spend the time to merge it with yours. Yes, I probably should think about modifying my code to take some of the improvements you suggest

Your "wrap" works because you are willing to require the user to pass the handle-container in as a typeglob (returning localised filehandles starts to hit the bugs). I didn't want to do that because the natural interface is a signature of (&) so that its single arg is a codeblock. To mimic the "open" builtin it'd need a signature of (*&) which would clutter user-code with the "sub" keyword.

Opinions my own; statements of fact may be in error.

In reply to Re^7: Un "tie"ing a "tie" by dpuu
in thread Un "tie"ing a "tie" by herby1620

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.