undefined | Better HN

0 pointsmatheusmoreira1y ago0 comments

Yeah, naming is hard. If there is a better word for "non-output", I don't know it.

0 comments

I would maybe call it stdlog or stdinfo vs stderr, but yeah naming things is hard.

I think stdinfo would exclude error messages from the definition, just like stderr excludes info messages.

I really like stdlog. Standard log stream is a pretty awesome name. Short and terse, the word "log" doesn't even need abbreviation and it's correct since it's a superset of error and info streams and also generic enough to cover other unforeseen categories.

I'll use it from now on!

packetlost1y ago

The idea for info is that it's informational, which is always the case regardless of whether it's printing error messages due to a failure or informational messages because the user specified a `-v` flag or whatever. Whether the command failed or not is communicated via the exit code. That being said, I do prefer stdlog for the reasons: it communicates the intent and usage as unambiguously and tersely as possible.

1 more reply

ryandrake1y ago

C++ has std::clog[1], but it's basically cerr, and the OS still only knows about stdin, stdout, and stderr.

1: https://cplusplus.com/reference/iostream/clog/

j / k navigate · click thread line to collapse

0 comments

packetlost1y ago

I would maybe call it stdlog or stdinfo vs stderr, but yeah naming things is hard.

matheusmoreiraOP1y ago

I think stdinfo would exclude error messages from the definition, just like stderr excludes info messages.

I'll use it from now on!

packetlost1y ago

1 more reply

ryandrake1y ago

C++ has std::clog[1], but it's basically cerr, and the OS still only knows about stdin, stdout, and stderr.

1: https://cplusplus.com/reference/iostream/clog/

j / k navigate · click thread line to collapse