-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<typeinfo>
unconditionally included on dinkumware
#306
Comments
I have reproduced the https://svn.boost.org/trac10/ticket/4115 problem by applying boostorg/lexical_cast#31 and #307 on VC9.0/10.0/11.0, the fix for LexicalCast proposed in boostorg/lexical_cast#32. |
I'm curious to know why you think injecting typeinfo into the namespace in which it really should be defined anyway is such a bad idea? |
I did not say it is a bad idea, it is convenient but costly. |
The IAR compiler for Arm uses Dinkumware and if I disable exceptions, which is admittedly I guess a non-standard extension, then it fails to compile this injection because it does not have |
Digging around more on this, I'm not sure that #307 is the right solution after all. I fixed this another way by a very simple modification to
but I think it should be:
What do you think, @jzmaddock? I believe you added that line 6 months ago. :) |
You're correct: that's supposed to detect old MSVC versions, checking for |
#307 is the right way, because Boost.TypeInfo is a portable solution to the problem the code is solving. |
|
Yes to |
Sure, I was just suggesting what I already saw used repeatedly within that file, but now I realize that they were testing the version of |
Even though we might agree about that line 89 needing a I'm inclined to agree with @Kojoley that their solution is the right way to go, but I think the PR needs to also remove all the references to So, I would be super happy about someone putting the |
I does confirm problem (IAR) and possibly solution works. |
It was added in 668b3fc to fix lexical_cast (https://svn.boost.org/trac10/ticket/4115) problem, but that seems to be an overkill (and probably not needed since boostorg/lexical_cast@3ce36a2?).
Also, it is a strange thing that with defined
BOOST_NO_STD_TYPEINFO
there isstd::typeinfo
. It completely undermines the purpose of the macro and ofboost/core/typeinfo.hpp
.The text was updated successfully, but these errors were encountered: