View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0029161 | Open CASCADE | OCCT:Coding | public | 2017-09-29 13:01 | 2023-08-01 15:09 |
| Reporter | kgv | Assigned To | |||
| Priority | normal | Severity | minor | ||
| Status | new | Resolution | open | ||
| Product Version | 7.2.0 | ||||
| Target Version | Unscheduled | ||||
| Summary | 0029161: Coding Rules - No_Exception is defined within packages ElSLib, HLRAlgo, HLRBRep, Intrv even for Debug target | ||||
| Description | The following pacakges unconditionally and without any comments define No_Exception macro: ElSLib, HLRAlgo, HLRBRep, Intrv.#ifndef No_Exception #define No_Exception #endif No_Exception is expected to be managed by OCCT building configuration parameters, not within the code - defining it within Debug builds effectively disables validation checks intended to protect against / reveal errors in code. This also introduces inconsistency of actual implementation of affected methods between specific packages and other parts of OCCT. Thus, places currently defining No_Exception might be a subject for unreveleaed memory issues. | ||||
| Tags | No tags attached. | ||||
| Test case number | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-09-29 13:01 | kgv | New Issue | |
| 2017-09-29 13:01 | kgv | Assigned To | => kgv |
| 2017-09-29 13:01 | kgv | Description Updated | |
| 2017-09-29 13:02 | kgv | Summary | Coding Rules - No_Exception is defined within => Coding Rules - No_Exception is defined within packages ElSLib, HLRAlgo, HLRBRep, Intrv even for Debug target |
| 2019-07-10 19:27 |
|
Target Version | 7.4.0 => 7.5.0 |
| 2020-08-28 16:32 | kgv | Target Version | 7.5.0 => 7.6.0 |
| 2021-08-24 14:59 | kgv | Target Version | 7.6.0 => 7.7.0 |
| 2022-08-17 12:01 | kgv | Target Version | 7.7.0 => 7.8.0 |
| 2022-10-19 15:56 |
|
Assigned To | kgv => vpozdyayev |
| 2023-08-01 15:09 | dpasukhi | Target Version | 7.8.0 => Unscheduled |
