| Anonymous | Login | Signup for a new account | 11-10-2008 10:47 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000340 | [uClibc++] Documentation | minor | always | 07-12-05 13:05 | 08-02-05 20:13 | ||||
| Reporter | tommi | View Status | public | ||||||
| Assigned To | gkajmowi | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 0.1.11 | ||||||
| Summary | 0000340: std::runtime_error not derived from std::exception | ||||||||
| Description |
std::runtime_error needs to be derived from std::exception. This change follows the need to specify a throw-specifier in ~runtime_error. By the way: is it better not to declare a virtual do-nothing-destructor at all or decleare it inline like in std::range_error or define it it the cpp-file like std::runtime_error? I feel, that removing the destructors might be best. Then the virtual table points to the destructor of the base-class std::exception and no code needs to be generated for derived destructors. |
||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |