Title
quick_exit support for freestanding implementations
Status
c++11
Section
[compliance]
Submitter
Alisdair Meredith

Created on 2009-11-12.00:00:00 last changed 162 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Ammend p3 Freestanding implementations [compliance]

3 The supplied version of the header <cstdlib> shall declare at least the functions abort(), atexit(), at_quick_exit, and exit(), and quick_exit([support.start.term]). The other headers listed in this table shall meet the same requirements as for a hosted implementation.

Date: 2009-12-11.00:00:00

[ 2009-12-11 Moved to Tentatively Ready after 5 positive votes on c++std-lib. ]

Date: 2009-11-12.00:00:00

Addresses UK 172

This issue is a response to NB comment UK-172

The functions quick_exit and at_quick_exit should be added to the required features of <cstdlib> in a freestanding implementation.

This comment was rejected in Summit saying neither at_exit nor at_quick_exit should be required. This suggests the comment was misread, as atexit is already required to be supported. If the LWG really did wish to not require the registration functions be supported, then a separate issue should be opened to change the current standard.

Given both exit and atexit are required, the UK panel feels it is appropriate to require the new quick_exit facility is similarly supported.

History
Date User Action Args
2011-08-23 20:07:26adminsetstatus: wp -> c++11
2010-10-21 18:28:33adminsetmessages: + msg1365
2010-10-21 18:28:33adminsetmessages: + msg1364
2009-11-12 00:00:00admincreate