Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

comment on

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

Hello jobsworth,

Perhaps this will shed some light:

(1) Without warnings:

23:59 >perl -E "$c = 1; say(length $c);" 1 23:59 >perl -E "say(length $c);" 23:59 >perl -E "$c = sprintf('%d', $c); say(length $c);" 1 23:59 >

(2) With warnings:

23:59 >perl -wE "$c = 1; say(length $c);" 1 0:01 >perl -wE "say(length $c);" Name "main::c" used only once: possible typo at -e line 1. Use of uninitialized value in say at -e line 1. 0:01 >perl -wE "$c = sprintf('%d', $c); say(length $c);" Use of uninitialized value $c in sprintf at -e line 1. 1 0:01 >

Hope that helps,

Athanasius <°(((><contra mundum Iustus alius egestas vitae, eros Piratica,

In reply to Re: sprintf number to string by Athanasius
in thread sprintf number to string by jobsworth

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.