incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Vitek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (STDCXX-240) #define _RWSTD_NO_EXCEPTIONS when exceptions are disabled via command line option
Date Tue, 04 Dec 2007 00:01:53 GMT

     [ https://issues.apache.org/jira/browse/STDCXX-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Travis Vitek updated STDCXX-240:
--------------------------------

    Attachment: stdcxx-240.patch

Well, the test suite doesn't build cleanly if _RWSTD_NO_EXCEPTIONS is defined. There are many
undefined variable warnings, and many places that use keywords try/throw/catch without checking
the macro first.


I can't fully say that this is working completely because many of the tests don't compile
when _RWSTD_NO_EXCEPTIONS is defined. I also get some warnings because of mismatches. On AIX,
for example, I get these warnings.

"/amd/devco/vitek/stdcxx/trunk/include/new", line 216.7: 1540-0419 (W) An exception-specification
must be specified as "throw(std::bad_alloc)" to match the implicit declaration.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 216.7: 1540-1088 (W) The exception specification
is being ignored.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 223.6: 1540-0419 (W) An exception-specification
must be specified as "throw()" to match the implicit declaration.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 223.6: 1540-1088 (W) The exception specification
is being ignored.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 240.7: 1540-0419 (W) An exception-specification
must be specified as "throw(std::bad_alloc)" to match the implicit declaration.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 240.7: 1540-1088 (W) The exception specification
is being ignored.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 250.6: 1540-0419 (W) An exception-specification
must be specified as "throw()" to match the implicit declaration.
"/amd/devco/vitek/stdcxx/trunk/include/new", line 250.6: 1540-1088 (W) The exception specification
is being ignored.

Not sure how to proceed with this. I'm attaching the patch that checks the above mentioned
macros in the appropriate config headers. It does nothing else.

> #define _RWSTD_NO_EXCEPTIONS when exceptions are disabled via command line option
> ---------------------------------------------------------------------------------
>
>                 Key: STDCXX-240
>                 URL: https://issues.apache.org/jira/browse/STDCXX-240
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 4.1.2, 4.1.3, 4.1.4
>            Reporter: Martin Sebor
>            Assignee: Travis Vitek
>            Priority: Minor
>             Fix For: 4.2.1
>
>         Attachments: stdcxx-240.patch
>
>
> Moved from the Rogue Wave bug tracking database:
> Class/File: stdcomp.h
> Fix Priority: Can Fix
> Long Description: 
>   *** Dec 1 1999 6:03PM *** sebor ***
> A request for enhancement.
> Subject: define RWSTD_NO_EXCEPTIONS when __HPACC_NOEH is
> Date: Wed, 01 Dec 1999 17:11:36 -0800
> From: Chichiang Wan <wanc@cup.hp.com>
> Organization: California Language Labs
> To: oemsupport <oemsupport@roguewave.com>
> CC: dhandly@cup.hp.com, wanc_at_hp <wanc@cup.hp.com>
> aCC has an option +noeh.  When it is provided, __HPACC_NOEH will be
> defined.  It would be nice for users to need to only use +noeh.  For
> that,  
> RWSTD_NO_EXCEPTIONS needs to be defined conditionally. 
> =========================================================
> $ cat test.C
> #include <string>
> $ aCC +noeh -c test.C
> Error 46: "/opt/aCC/include/memory", line 493 # Exception handling is 
> not
>     enabled (do not use the +noeh flag to aCC).
>       RWSTD_THROW_NO_MSG(tmp == 0, bad_alloc);
> -- Chichiang
> ****Modified By: sebor @ May 29, 2000 10:28:25 PM****
> We should do this AND test it -- not just on aCC but in general with all compilers that
support this feature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message