Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I recently moved to CSW blastwave repositories - including perl.

I have a perl script that accepts a C program and does a pretty print to a network printer using lp().

The postscript is capture in a HERE doc.

$prolog = << ENDPROLOG; . . . A bunch of postscript. . . . ENDPROLOG $PRINT_CMD = '/usr/bin/lp'; $outcmd = "| $PRINT_CMD"; open(OUT,$outcmd); print OUT $prolog;
After upgrading perl the script is no longer printing the postscript but is printing the postscript code.

I was wondering if someone could point me to a better way.


In reply to piping to lp is broken after perl upgrade by myuserid7

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.