Closed
Bug 604829
Opened 15 years ago
Closed 15 years ago
more helpful usage info for js -h
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dherman, Assigned: dherman)
Details
(Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file)
|
5.16 KB,
patch
|
jorendorff
:
review+
|
Details | Diff | Splinter Review |
The JS shell produces a pretty cryptic usage info, and I can never remember which toggles take which characters. I'll submit a patch with more detailed usage info.
Dave
| Assignee | ||
Comment 1•15 years ago
|
||
Assignee: general → dherman
Comment 2•15 years ago
|
||
dherman++
| Assignee | ||
Updated•15 years ago
|
Attachment #483678 -
Flags: review?(jorendorff)
Comment 3•15 years ago
|
||
Comment on attachment 483678 [details] [diff] [review]
proposed usage info
>+ fprintf(gErrFile, " -w Report strict warnings\n");
>+ fprintf(gErrFile, " -W Do not report strict warnings\n");
>+ fprintf(gErrFile, " -x Toggle JSOPTION_XML flag\n");
>+ fprintf(gErrFile, " -C Compile-only; do not execute\n");
>+ fprintf(gErrFile, " -i Enable interactive read-eval-print loop\n");
Instead of this, please say:
>+ fprintf(gErrFile, " -w Report strict warnings\n"
>+ " -W Do not report strict warnings\n"
>+ " -x Toggle JSOPTION_XML flag\n"
>+ " -C Compile-only; do not execute\n"
>+ " -i Enable interactive read-eval-print loop\n"
...
until you get down to the part where you're actually printf-ing something, of course. r=me with that, and thanks.
Attachment #483678 -
Flags: review?(jorendorff) → review+
| Assignee | ||
Comment 4•15 years ago
|
||
Whiteboard: fixed-in-tracemonkey
Comment 5•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•