Closed Bug 329718 Opened 18 years ago Closed 11 years ago

explicit error-handling semantics

Categories

(Toolkit :: Safe Browsing, enhancement)

Product:
Toolkit
Component:
Safe Browsing
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Milestone:
Future

People

(Reporter: fritz, Unassigned)

Details

We need more consistent semantics for errors. What's the right way to flag them (return value or exceptions)? Who can throw what kind of errors? Who can catch exceptions and how (e.g., can we have naked exception handlers)?
QA Contact: nobody → safe.browsing
Target Milestone: --- → Future
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.