[
https://issues.apache.org/jira/browse/STDCXX-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582764#action_12582764
]
Martin Sebor commented on STDCXX-643:
-------------------------------------
I meant in a regular test (not a config one). But you're right, that may not be
enough. Similarly, asserting the same conditions in a config test wouldn't be
enough unless the test's failure caused the whole configuration process to
fail. We don't have a mechanism like that in place but we've had the need for
it in the past so enhancing the config infrastructure might be the way to go.
The other approach you suggest -- to {{#define}} a macro like
{{_RWSTD_NO_EXCEPTION_BROKEN}} and then asserting that it's {{#defined}} (or
preferably the other way around so as not to introduce unnecessary macros)
would also work.
That said, if as you say we already have a solution in place for other types (I
forgot about {{struct lconv}} and {{struct tm}}), we might as well use it.
> std::exception declaration incompatible with implementation provided by
> runtime library on AIX
> ----------------------------------------------------------------------------------------------
>
> Key: STDCXX-643
> URL: https://issues.apache.org/jira/browse/STDCXX-643
> Project: C++ Standard Library
> Issue Type: Bug
> Components: 19. Diagnostics
> Affects Versions: 4.2.0
> Environment: AIX
> Reporter: Travis Vitek
> Fix For: 5.0
>
>
> A description of the problem is available here.
> http://www.nabble.com/19.exceptions.mt.cpp-fails-on-AIX-tf4738595.html
> Essentially we need to add a const char* member to std::exception for AIX.
> Unfortunately the fix is a binary incompatible with previous versions of
> stdcxx.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
