Wed, 03/16/2011 - 22:30
FYI: Compiling with 'clang' on OS X, I encountered the following errors; I know that 'clang' is not a supported compiler, but I think they point to a real problem in the code.
../../../src/Visual3d/Visual3d_TransientManager.cxx:123:47: error: taking the address of a temporary object of type 'Aspect_CLayer2d' (aka 'CALL_DEF_LAYER') [-Waddress-of-temporary]
theCView.ptrUnderLayer = (CALL_DEF_LAYER *) &(UnderLayer->CLayer ());
^ ~~~~~~~~~~~
../../../src/Visual3d/Visual3d_TransientManager.cxx:127:46: error: taking the address of a temporary object of type 'Aspect_CLayer2d' (aka 'CALL_DEF_LAYER') [-Waddress-of-temporary]
theCView.ptrOverLayer = (CALL_DEF_LAYER *) &(OverLayer->CLayer ());
^ ~~~~~~~~~~~
../../../src/Visual3d/Visual3d_TransientManager.cxx:192:46: error: taking the address of a temporary object of type 'Aspect_CLayer2d' (aka 'CALL_DEF_LAYER') [-Waddress-of-temporary]
theCView.ptrUnderLayer = (CALL_DEF_LAYER *)&(AView->UnderLayer()->CLayer());
^ ~~~~~~~~~~
../../../src/Visual3d/Visual3d_TransientManager.cxx:194:45: error: taking the address of a temporary object of type 'Aspect_CLayer2d' (aka 'CALL_DEF_LAYER') [-Waddress-of-temporary]
theCView.ptrOverLayer = (CALL_DEF_LAYER *)&(AView->OverLayer()->CLayer());
^ ~~~~~~~~~~
../../../src/Visual3d/Visual3d_TransientManager.cxx:232:47: error: taking the address of a temporary object of type 'Aspect_CLayer2d' (aka 'CALL_DEF_LAYER') [-Waddress-of-temporary]
theCView.ptrUnderLayer = (CALL_DEF_LAYER *) &(AView->UnderLayer()->CLayer ());
^ ~~~~~~~~~~~
../../../src/Visual3d/Visual3d_TransientManager.cxx:234:46: error: taking the address of a temporary object of type 'Aspect_CLayer2d' (aka 'CALL_DEF_LAYER') [-Waddress-of-temporary]
theCView.ptrOverLayer = (CALL_DEF_LAYER *) &(AView->OverLayer()->CLayer ());
^ ~~~~~~~~~~~
Thu, 03/17/2011 - 16:18
Hi Jens,
I would like to inform you that the posted problem is checked and we confirm that it is the real bug.
The corresponding issue with ID = OCC22330 has been registered.
Later you can know if the issue is resolved by checking references to the specified ID in OCCT Release Notes. The analysis of the issue will take some time depending on our technical capability and availability of resources.
Regards