[ITK-dev] Workaround for dynamic_cast on Mac OSX
Johnson, Hans J
hans-johnson at uiowa.edu
Thu Nov 10 15:21:42 EST 2016
I agree with Marcus. At least until it is very clear that not using dynamic_cast is the only solution to a broken compiler, I am very weary of “doing what works today”.
Hans
--
On 11/10/16, 1:11 PM, "Insight-developers on behalf of Marcus D. Hanwell" <insight-developers-bounces at itk.org on behalf of marcus.hanwell at kitware.com> wrote:
On Tue, Nov 8, 2016 at 5:01 PM, Matt McCormick
<matt.mccormick at kitware.com> wrote:
> Hi folks,
>
> As we have wrestled with in Slicer, along with other applications
> where ITK is used in multiple shared libraries, dynamic_cast can fail
> on Mac OSX.
>
> I summarized the cause of the problem and steps for the proposed solution here:
>
> https://issues.itk.org/jira/browse/ITK-3490
>
> Feedback is welcome. The effort is targeted for the ITK 4.11.0 release.
>
From the issue it is not clear to me why you can't fix the symbol
visibility issues, or which of these cases it causing the breakage.
Reading the linked blog post it seems like Apple/Clang is doing the
right thing, and C++ libraries must be careful to use consistent
symbol visibility.
I would be interested in further details on which case or cases are
causing dynamic_cast to fail, and why using consistent symbol
visibility in the interfaces is not feasible/possible.
Thanks,
Marcus
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Kitware offers ITK Training Courses, for more information visit:
http://kitware.com/products/protraining.php
Please keep messages on-topic and check the ITK FAQ at:
http://www.itk.org/Wiki/ITK_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/insight-developers
More information about the Insight-developers
mailing list