Closed
Bug 263242
Opened 21 years ago
Closed 21 years ago
How about if trapdoor didn't SEGV with no arguments?
Categories
(Webtools Graveyard :: Bonsai, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 128747
People
(Reporter: kiko, Assigned: kiko)
Details
Attachments
(2 files)
|
584 bytes,
patch
|
cls
:
review-
|
Details | Diff | Splinter Review |
|
570 bytes,
patch
|
cls
:
review-
|
Details | Diff | Splinter Review |
Wouldn't it be nice if trapdoor didn't SEGV with no arguments?
| Assignee | ||
Comment 1•21 years ago
|
||
| Assignee | ||
Updated•21 years ago
|
Attachment #161316 -
Flags: review?(timeless)
Comment on attachment 161316 [details] [diff] [review]
kiko_v1: dull hack
That message should use the standard usage syntax:
Usage: $0 passwd
Attachment #161316 -
Flags: review?(timeless) → review-
| Assignee | ||
Comment 3•21 years ago
|
||
| Assignee | ||
Updated•21 years ago
|
Attachment #161329 -
Flags: review?(cls)
Comment on attachment 161329 [details] [diff] [review]
kiko_v2: sure
The first printf is not necessary. The fact that an argument is missing should
be clear by the standard Usage line. Also, the test should be for argc != 2.
Attachment #161329 -
Flags: review?(cls) → review-
| Assignee | ||
Comment 5•21 years ago
|
||
Don't you think you're being a bit too picky about something that currently
segmentation faults? :-)
See what happens when you ask for reviews? :-P In truth, I'm being really picky
about something I plan to replace at my earliest convenience (see bug 128747).
Besides that, I just don't see the point of the customized verbose error message
when a standard one would do.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 7•21 years ago
|
||
Let's do that, then.
*** This bug has been marked as a duplicate of 128747 ***
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•