#4 print errors to stderr, not stdout

open
None
5
2005-06-02
2005-03-15
Anonymous
No

It's reasonable to assume many people will build sparklines once and
cache them, using the php command line utility like so:

php deficit.php > deficit.png

If this execution fails (perhaps because it can't find an existing log
file), the person executing the command doesn't see an error,
because it's been routed into what she presumes to be an image file.
The warning should be written on stderr, where she will see it, not to
stdout, where it'll more than likely get mixed up with image data.

Discussion

  • James Byers

    James Byers - 2005-06-02
    • assigned_to: nobody --> jbyers
     
  • James Byers

    James Byers - 2005-06-02

    Logged In: YES
    user_id=157

    Agreed, though this will require more changes than I'm
    prepared to make for 0.2. Will address in 0.3.

    James

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks