MantisBT
Mantis Bug Tracker Workflow

View Revisions: Issue #29161 All Revisions ] Back to Issue ]
Summary 0029161: Coding Rules - No_Exception is defined within packages ElSLib, HLRAlgo, HLRBRep, Intrv even for Debug target
Revision 2017-09-29 13:01 by kgv
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.
Revision 2017-09-29 13:01 by kgv
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.


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker