View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0030842CommunityOCCT:Codingpublic2019-07-12 10:282019-10-08 10:47
Reporterdenix56 Assigned Todenix56  
PrioritynormalSeverityminor 
Status closedResolutionno change required 
PlatformWindowsOSVC++ 2015 
Product Version7.3.0 
Summary0030842: C++11 support
DescriptionHi all,

I wonder if OpenCascade is going to require C++11 in future releases, because all the major compilers completely support C++11 and most of them - C++14.

It will definitely improve the code stricture and give some new possibilities.
For example, I`ve made a patch for OSD_Thread (no TBB) to support exception handling. It requires to use std::shared_ptr and std::exception_ptr, that are C++11 features. It will be useful, because when you launch any algorithm in parallel and it throws the exception you cannot handle it correctly.
TagsNo tags attached.
Test case number

Relationships

related to 0029935 closedbugmaster Open CASCADE Foundation Classes - introduce OSD_ThreadPool class defining a thread pool 
related to 0025896 closedabv Community Modeling Algorithms - UserBreak raising uncatchable exception in boolean operations 

Activities

kgv

2019-07-12 10:46

developer   ~0085609

Last edited: 2019-07-12 10:47

 OCCT already uses C++11 features (deliberately).

However, as some projects based on OCCT requires support of outdated compilers, we cannot force users and require fully C++11-complient compilers yet.
Therefore, a limited compatibility with such compilers is currently maintained.

> For example, I`ve made a patch for OSD_Thread (no TBB) to support exception handling.
> It requires to use std::shared_ptr and std::exception_ptr, that are C++11 features.
> It will be useful, because when you launch any algorithm in parallel and it throws the exception you cannot handle it correctly.
Patches are welcome.
Currently OSD_ThreadPool re-raises all catches exceptions as Standard_ProgramError, and aggregates the text of multiple exceptions if they have occurred concurrently threads (potentially they can be of different kind, it is unclear which exception should have higher priority to be re-raised for preserving type).

denix56

2019-08-02 13:11

reporter   ~0085984

Tnasks, for the info.

I`ve also found the topics related to my problem and proposed the patch there

denix56

2019-10-08 09:36

reporter   ~0087936

Close the bug please

Issue History

Date Modified Username Field Change
2019-07-12 10:28 denix56 New Issue
2019-07-12 10:28 denix56 Assigned To => kgv
2019-07-12 10:46 kgv Note Added: 0085609
2019-07-12 10:47 kgv Note Edited: 0085609
2019-07-12 10:48 kgv Relationship added related to 0029935
2019-07-16 13:43 kgv Assigned To kgv => denix56
2019-07-16 13:43 kgv Status new => feedback
2019-08-02 13:11 denix56 Note Added: 0085984
2019-09-04 12:24 kgv Relationship added related to 0025896
2019-10-08 09:36 denix56 Note Added: 0087936
2019-10-08 10:47 abv Status feedback => closed
2019-10-08 10:47 abv Resolution open => no change required