Closed Bug 583436 Opened 14 years ago Closed 5 years ago

Properly handle exceptions in narcissus

Categories

(Other Applications Graveyard :: Narcissus, defect)

Product:
Other Applications Graveyard
Component:
Narcissus
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: shu, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b3pre) Gecko/20100730 Minefield/4.0b3pre
Build Identifier: 

The eval function can throw errors which are catchable. The current narcissus exception code handles this very ad-hoc, should redo.

Should also improve the lexer's newSyntaxError to play nice with eval.

Reproducible: Always
Keywords: narcissus
Some test cases, copied from the (dup) bug 584116:

    try { undefined() } catch (e) { print("caught") }
    try { unbound } catch(e) { print("caught") }

Dave
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Oops, marked wrong one as dup.

Dave
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: DUPLICATE → ---
Assignee: general → nobody
Component: JavaScript Engine → Narcissus
Product: Core → Other Applications
QA Contact: general → narcissus
Keywords: narcissus
Blocks: 584777
Closing as Narcissus isn't maintained anymore.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 5 years ago
Resolution: --- → WONTFIX
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.