Opened 9 years ago
Closed 9 years ago
#2013 closed enhancement (fixed)
Improve error message quality of exceptions
Reported by: | jng | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | 2.4 |
Component: | General | Version: | |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description (last modified by )
There are a series of exceptions thrown in MapGuide that could be easily improved in terms of clarity. For example:
- MgNullArgumentException? - Should include the identifier that failed the null pointer check
- MgNullReferenceException? - Should include the identifier that failed the null reference check
- MgArgumentOutOfRangeException? - Should include the identifier that failed the range check
- MgObjectNotFoundException? - Should include the name whose associated object could not be found
Most of these exceptions are thrown by pre-defined macros like CHECKARGUMENTNULL(), etc. So a simple modification to these macros where applicable to include the stringified argument being checked will result in clearer error messages being included.
Change History (3)
comment:1 Changed 9 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 9 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Fixed in trunk (r6715) and 2.4 (r6711 and r6713)