in C++ there's std::cout, std::cerr and std::clog,
and I use all three in my private projects.
p
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, Jun 23, 2011 at 01:44:59PM +0200, Jan Nieuwenhuizen wrote:
Carl Sorensen writes:
it should redirect non-error output to the file, and errors should appear
in the terminal.
Stdout is used for valuable program output, stderr for any kind of
message, including progress. The name
- Original Message -
From: Graham Percival gra...@percival-music.ca
0. (meta-question) do we think that we can resolve this once and
for all right now, or should we wait a month to cover it as a
GOP-PROP ? If we discuss it now, then I do *not* want to have it
left hanging (as we've
On Sat, Jun 25, 2011 at 05:27:03PM +0100, Graham Percival wrote:
1. what's the official unix definition of STDERR vs. STDOUT?
Quoting the standard:
3.358 Standard Error
An output stream usually intended to be used for diagnostic messages.
[...]
3.360 Standard
Graham Percival graham at percival-music.ca writes:
Stdout is used for valuable program output, stderr for any kind of
message, including progress. The name stdERR is possibly somewhat
unfortunate and comes from the days that unix commands would only
print something (to stdERR) if
Graham Percival writes:
I think we need to go here.
No. There will be no progress, warning or error messages to stdout.
3. do we believe in the general unix statement no news is good
news, in which case why does lilypnond foo.ly spam out 16 lines
of text? (regardless of whether that spam
On Sat, Jun 25, 2011 at 08:58:43PM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
I think we need to go here.
No. There will be no progress, warning or error messages to stdout.
But we *do* have progress messages on stderr. This makes sense to
some people, but doesn't make
Am Samstag, 25. Juni 2011, 19:21:53 schrieb Phil Holmes:
I think we need to cover it properly - based on past experience it's likely
to generate some heated discussion.
Yes, I also think that we should properly discuss the console output of
lilypond and probably different log levels.
I also
Am Samstag, 25. Juni 2011, 20:09:50 schrieb Matthias Kilian:
On Sat, Jun 25, 2011 at 05:27:03PM +0100, Graham Percival wrote:
1. what's the official unix definition of STDERR vs. STDOUT?
Quoting the standard:
3.358 Standard Error
An output stream usually intended to be used
Jan Nieuwenhuizen jann...@gnu.org writes:
Graham Percival writes:
I think we need to go here.
No. There will be no progress, warning or error messages to stdout.
stdout is usually line-buffered (like stdin), so progress messages are
not really useful.
The GNU utilities take the
10 matches
Mail list logo
