[ 
https://issues.apache.org/jira/browse/PROTON-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320716#comment-14320716
 ] 

ASF subversion and git services commented on PROTON-772:
--------------------------------------------------------

Commit bc91eb69d068abbd6439f7244d1284e53ff5d407 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=bc91eb6 ]

Revert "PROTON-772: Remove all direct printing to stdout and stderr (missed 
one)"
This reverts commit a0e7cced9d9840c7a81185e83a6371ef5fbc96ca.

- This change isn't necessary because pn_transport_log() is the bottom of
  the transport logging stack and the check for tracing flags is above.


> Remove all direct printing to stdout and stderr.
> ------------------------------------------------
>
>                 Key: PROTON-772
>                 URL: https://issues.apache.org/jira/browse/PROTON-772
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.8
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.3
>
>
> A library should never, ever print anything directly to stdout/stderr unless 
> explicitly requested to do so, as it may be linked with programs that need to 
> control what they output to stdout/err or programs that have no stdout/err at 
> all.
> Failures should be raised  via the API error mechanism with appropriate 
> message strings that the caller can display as they see fit. Informational 
> log messages should be logged in a way that the caller can send them where 
> they want or turn them off if they want.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to