It needs the -w option to do so, currently. The lack of warnings has hurt us already, in getting the testsuite back on its feet. I say we should just fix this fast, not in absolute nsbeta2/3 priority order. But I'm not sure the PDT will agree -- I'm currently arguing with phil about how trivial fixes should not be starved by high priority, less easily fixed bugs. Obviously, not all small fixes are trivial, and too many truly trivial fixes can starve out higher priority bugs, but I think the PDT is erring on the other side, at the moment. /be
[SPAM] Marking milestone 'future' as part of nsbeta3 triage.
Target Milestone: --- → Future
What's the right new flag for 'suppress warnings?' I'm leaning towards -W. -nw wouldn't be consistent; other args are single-char. Could do --no-warnings, by itself or in addition.
-W is ok with me, but maybe we should use getopt_long on Linux etc.? /be
Fix checked in. Leaving getopt_long for another round of js.c changes. I left the -w option intact, in case somebody was using it.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.