Bug 1620583 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Our current error reporting code is very old and quite complicated. Here is a first list of ideas on how to improve this:

- Remove "extra" warnings
- Remove "werror"
- Remove JSREPORT_* flags
- Separate error and warning reporting
- Simpler error reporting API like `ThrowError(cx, JSMSG_UNDECLARED_VAR, "xyz");`
- Make JSReportError type better with ownership and less manual memory management
- UTF8 vs Latin1
Revision 1 by
on 
Our current error reporting code is very old and quite complicated. Here is a first list of ideas on how to improve this:

- Remove "extra" warnings
- Remove "werror"
- Remove JSREPORT_* flags
- Separate error and warning reporting
- Simpler error reporting API like `ThrowError(cx, JSMSG_UNDECLARED_VAR, "xyz");`
- Make JSErrorReport type better with ownership and less manual memory management
- UTF8 vs Latin1
Revision 2 by
on 
Our current error reporting code is very old and quite complicated. Here is a first list of ideas on how to improve this:

- ~~Remove "extra" warnings~~
- ~~Remove "werror"~~
- Remove JSREPORT_* flags
- Separate error and warning reporting
- Simpler error reporting API like `ThrowError(cx, JSMSG_UNDECLARED_VAR, "xyz");`
- Make JSErrorReport type better with ownership and less manual memory management
- UTF8 vs Latin1
Revision 3 by
on 
Our current error reporting code is very old and quite complicated. Here is a first list of ideas on how to improve this:

- ~~Remove "extra" warnings~~
- ~~Remove "werror"~~
- ~~Remove JSREPORT_* flags~~
- Separate error and warning reporting
- Simpler error reporting API like `ThrowError(cx, JSMSG_UNDECLARED_VAR, "xyz");`
- Make JSErrorReport type better with ownership and less manual memory management
- UTF8 vs Latin1

Back to Bug 1620583 Comment 0