You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scala should print usage information to stdout instead of stderr. While errors about command line arguments should be printed to stderr, when explicitly asked for help this info should go to stdout. This allows it to be piped to grep or less, etc. It's also in the GNU coding standards, and seems to be a lot more useful in general.
@dragos said (edited on Feb 10, 2017 2:18:14 PM UTC):
I would deviate from Java on this point, since the intention of passing -X or -Y is really to get usage information. I also grep those way more often than the regular ones. I guess stderr made sense if scalac output was pipeable to other processes and errors/diagnostics would confuse them. However, for scalac the only output that's worth piping is usage information.
Scala should print usage information to stdout instead of stderr. While errors about command line arguments should be printed to stderr, when explicitly asked for help this info should go to stdout. This allows it to be piped to grep or less, etc. It's also in the GNU coding standards, and seems to be a lot more useful in general.
http://www.gnu.org/prep/standards/html_node/_002d_002dhelp.html
The text was updated successfully, but these errors were encountered: