Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

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

Several small fixes, but 0.94 might fix more than you needed

0.95 - 2013-01-13

  • Introduce allow_unquoted_escape as workaround for RT#81295
  • Update copyright to 2013
  • Introduce print_hr () for RT#76143
  • Dropped plans to support EBCDIC

0.94 - 2012-12-03

  • Guard against beta releases of Encode (Xavier Guimard - RT#81499)
  • Fix sv_cache init global-buffer-overflow (Reini Urban - RT#81469)
  • Tested with perl compiled with clang (also to verify RT#81469)
  • Fix memory leak reported in RT#81539 (Fix by Tony Cook)

0.93 - 2012-11-19

  • Skip Encode related tests on too old Encode
  • Force old(er) tar format (ustar) - assumes GNU tar on release box

Enjoy, Have FUN! H.Merijn

In reply to Re: The future of Text::CSV_XS - TODO by Tux
in thread The future of Text::CSV_XS - TODO by Tux

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.