On 2/24/06, <b class="gmail_sendername">Kostis Anagnostopoulos</b> <<a href="mailto:ankostis@gmail.com">ankostis@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 2/23/06, Ceki Gülcü <<a href="mailto:listid@qos.ch">listid@qos.ch</a>> wrote:<br>> Is the 'stdout' 'stderr' distinction really important to you or is it more<br>> a matter of preference?<br><br>My answer is No. To both!
<br><br>Here is why i say no to both of your questions:<br><br>I'm making text-parsing code that is used at the same time to a<br>cmd-line utility and to an EJB. So,<br>-it is not important *for me* because i use slf4j-log4j.jar
in both<br>situations, and<br>-it is not just a matter of preference, because slf4j-simple.jar as it<br>is, is not an option for the cmd-line tool. This is a defect!<br><br>I consider 'simple' useful for when to run in
pre-1.4 VMs with no JDK<br>logging support and log4j is just too much.<br>That is why a really think the distinction is really important, in general.</blockquote><div><br>I'm OK only if the log messages are written to one file descriptor. stderr is also a good idea. For example, gcc, other GNU applications, and
java.util.loggging writes messages to stderr by default.<br><br>So here's my +1.<br><br>Trustin</div></div>-- <br>what we call human nature is actually human habit<br>--<br><a href="http://gleamynode.net/">http://gleamynode.net/
</a><br>--<br>PGP key fingerprints:<br>* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E<br>* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6