For developers using Windows 9x, COMMAND.COM can't redirect stderr, meaning that when you have a lot of compiler errors, you miss most of them as soon as they go off the screen, and have no means of capturing them. In this situation, it would be desirable to redirect stderr to stdout, and since COMMAND.COM can't do it, JMake must.
There might be other situations where a developer would prefer to redirect stderr into stdout within JMake rather than have to do it at the shell level, although I can't think of any off the top of my head.
The argument to redirect stderr to stdout would be something like -combine, -redirect, or an abbreviation. Thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For developers using Windows 9x, COMMAND.COM can't redirect stderr, meaning that when you have a lot of compiler errors, you miss most of them as soon as they go off the screen, and have no means of capturing them. In this situation, it would be desirable to redirect stderr to stdout, and since COMMAND.COM can't do it, JMake must.
There might be other situations where a developer would prefer to redirect stderr into stdout within JMake rather than have to do it at the shell level, although I can't think of any off the top of my head.
The argument to redirect stderr to stdout would be something like -combine, -redirect, or an abbreviation. Thoughts?
How about -stderr? (which would act exactly like 2>&1 does on shells that are less than completely braindead :P)
stderr sounds good...