explicit error-handling semantics

RESOLVED INVALID

Status

()

--
enhancement
RESOLVED INVALID
13 years ago
5 years ago

People

(Reporter: fritz, Unassigned)

Tracking

unspecified
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
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)?

Updated

13 years ago
QA Contact: nobody → safe.browsing
Target Milestone: --- → Future
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
Component: Phishing Protection → Phishing Protection
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.