- Title
- Incorrect example of unspecified behavior
- Status
- c++14
- Section
- 6.10.1 [intro.execution]
- Submitter
- Alisdair Meredith
Created on 2012-11-03.00:00:00 last changed 133 months ago
Messages
Date: 2013-09-15.00:00:00
[Moved to DR at the September, 2013 meeting.]
Date: 2013-04-15.00:00:00
Proposed resolution (April, 2013):
Change 6.10.1 [intro.execution] paragraph 3 as follows:
Certain other aspects and operations of the abstract machine are described in this International Standard as unspecified (for example,order of evaluation of arguments to a functionevaluation of expressions in a new-initializer if the allocation function fails to allocate memory (7.6.2.8 [expr.new])). Where possible...
Date: 2012-11-03.00:00:00
Currently, 6.10.1 [intro.execution] paragraph 3 says,
Certain other aspects and operations of the abstract machine are described in this International Standard as unspecified (for example, order of evaluation of arguments to a function).
However, the order of evaluation of function arguments is no longer “unspecified;” instead, their value computations are unsequenced. A better example of unspecified behavior is needed.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-11-24 00:00:00 | admin | set | status: drwp -> c++14 |
| 2014-03-03 00:00:00 | admin | set | status: dr -> drwp |
| 2013-10-14 00:00:00 | admin | set | messages: + msg4679 |
| 2013-10-14 00:00:00 | admin | set | status: ready -> dr |
| 2013-05-03 00:00:00 | admin | set | messages: + msg4305 |
| 2013-05-03 00:00:00 | admin | set | status: open -> ready |
| 2012-11-03 00:00:00 | admin | create | |