Replies: 5 comments 7 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Dmitry, For me, the biggest pain point is Thread-Safety, It is hard to debug and requires extra effort to design and work around these issues. For example, at the moment of writing, I am looking at TSan showing a data-race for BOPAlgo_Builder::Perform for the case when Parallel SetRunParallel is set to
For my use, OCAF. Primarily due to concurrency constraints.
No comment at the moment.
I would say ranges/views can be a significant improvement to TDF iterators. To give you a feeling, here is an example code from one of my tests where I use a custom This will iterate through all labels that have a PartAttribute that is a TDF_Attribute. It is more of a convenience improvement but I think it would go along with modernization nicely. Best regards! |
Beta Was this translation helpful? Give feedback.
-
|
I've just started using the library, so I haven't really used the API in depth. Here's a few suggestions that come to mind:
|
Beta Was this translation helpful? Give feedback.
-
|
Set color, material aspects .etc. for |
Beta Was this translation helpful? Give feedback.
-
|
I mentioned this in an issue, but will plug it here too: it would be great to get rid of all the functions/methods using pointers [handles] passed by reference. I suppose a modern equivalent would be to allocate in the functions and return a pointer or tuple of pointers. Cf. #985 (comment) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🚀 The Road to OCCT 8.0.0
As we ramp up development for Open CASCADE Technology 8.0.0, we are looking at a unique opportunity. Major releases are the right time to introduce breaking changes that improve the long-term health, performance, and usability of the library.
We have our own internal roadmap for modernization (C++17, infrastructure changes, etc.), but we want to ensure we are addressing the pain points that you—the community developers—face daily.
🏗️ What we are already considering
To give you an idea of the scope, here are some architectural changes currently on the table:
Standard_Failuretostd::exceptionfor error handling.NCollectioncontainers to support range-based for loops and standard algorithms.Abs,Min,Max) in favor ofstd::equivalents.🗣️ We want your input
If you could change one thing about the OCCT architecture that requires breaking backward compatibility, what would it be?
We are looking for feedback on:
Please share your thoughts, specific examples, or even pseudo-code below. Let's build a better foundation for the future of Open Source CAD.
Beta Was this translation helpful? Give feedback.
All reactions