Ok thanks for the heads up, for me it's just cosmetic.
-- Sent from my ParanoidAndroid Galaxy Nexus with K-9 Mail.
Rich Mattes <firstname.lastname@example.org> wrote:
On Wed, Sep 26, 2012 at 5:18 AM, Claudio Carbone <email@example.com>
what you tell me is apparently what I do.
Here is a code snippet from the FSM
Now the fact is that even when everything is fine and I intercept no
errors, I get this line
playerc warning : warning : [Player v.3.1.0-svn] connected on
[localhost:6665] with sock 14
which is obviously from the player library.
I wanted to get rid of that is at all possibile.
Those messages come from client_libs/libplayerc/error.h. The macros in there store the error string and then print it to stderr. You could start your process and redirect stderr to /dev/null if the issue is a cosmetic one. Otherwise you can modify error.h and get rid of the fprintf calls.
If it's really an issue I can change error.h to look something like:
#if defined PLAYERC_NO_STDERR
#define PLAYERC_ERR(msg) snprintf(...,msg)
#define PLAYERC_ERR(msg) snprintf(...,msg), fprintf(stderr, ... ,msg)
Then if you define PLAYERC_NO_STDERR before you include libplayerc/playerc.h, you won't have any terminal output from the playerc library.
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
Playerstage-users mailing list