Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r60454 - in sandbox/committee: LWG/proposals concepts/wording exceptions rvalue_ref
From: dgregor_at_[hidden]
Date: 2010-03-10 21:47:44

Next message: joel_at_[hidden]: "[Boost-commit] svn:boost r60455 - trunk/libs/spirit/example/scheme"
Previous message: eric_at_[hidden]: "[Boost-commit] svn:boost r60453 - trunk/libs/proto/doc/reference/concepts"

Author: dgregor
Date: 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
New Revision: 60454
URL: http://svn.boost.org/trac/boost/changeset/60454

Log:
First stab at deprecating exception specifications
Added:
   sandbox/committee/exceptions/
   sandbox/committee/exceptions/Makefile (contents, props changed)
   sandbox/committee/exceptions/d3051.html (contents, props changed)
   sandbox/committee/exceptions/deprecating-exception-specs.rst (contents, props changed)
   sandbox/committee/exceptions/rst.css (contents, props changed)
Text files modified:
   sandbox/committee/LWG/proposals/Makefile | 3 +++
   sandbox/committee/concepts/wording/Makefile | 5 ++++-
   sandbox/committee/concepts/wording/local.bib | 19 +++++++++++++++++++
   sandbox/committee/rvalue_ref/throwing-move.rst | 12 ++++++------
   4 files changed, 32 insertions(+), 7 deletions(-)

Modified: sandbox/committee/LWG/proposals/Makefile
==============================================================================
--- sandbox/committee/LWG/proposals/Makefile (original)
+++ sandbox/committee/LWG/proposals/Makefile 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -1,3 +1,6 @@
+noexcept.html: noexcept.rst
+ rst2html.py --stylesheet=exported-concept-maps.css --embed-stylesheet noexcept.rst noexcept.html
+
all: exported-concept-maps.html taxonomy-of-concepts-and-maps.html explicit-refinement.html

exported-concept-maps.html: exported-concept-maps.rst exported-concept-maps.css

Modified: sandbox/committee/concepts/wording/Makefile
==============================================================================
--- sandbox/committee/concepts/wording/Makefile (original)
+++ sandbox/committee/concepts/wording/Makefile 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -2,7 +2,10 @@

PDFLATEX = pdflatex

-basic: wording.pdf
+basic: deleted-special-member-funcs.pdf
+
+deleted-special-member-funcs.pdf: deleted-special-member-funcs.tex
+ @$(PDFLATEX) deleted-special-member-funcs.tex

wording.pdf: wording.tex macros.tex
@$(PDFLATEX) wording.tex

Modified: sandbox/committee/concepts/wording/local.bib
==============================================================================
--- sandbox/committee/concepts/wording/local.bib (original)
+++ sandbox/committee/concepts/wording/local.bib 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -404,6 +404,25 @@
   month = {March}
}

+@TechReport{GregorStroustrup08:concepts_wording_rev_9,
+ author = {Douglas Gregor and Bjarne Stroustrup and James Widman and Jeremy Siek},
+ title = {Proposed Wording for Concepts (Revision 9)},
+ institution = {ISO/IEC JTC 1, Information Technology, Subcommittee
+ SC 22, Programming Language {C++}},
+ year = 2008,
+ number = {N2773=08-0283},
+ month = {September}
+}
+
+
+
+@Unpublished{Gregor06:ImplicitAssignAndConstruct,
+ author = {Douglas Gregor},
+ title = {Implicit Assignments and Construction},
+ note = {\url{http://conceptgcc.wordpress.com/2006/05/04/implicit-assignments-and-construction/}},
+ month = {May},
+ year = 2006}
+
@TechReport{gregor08:soundness,
   author = {Douglas Gregor},
   title = {Type-Soundness and Optimization in the Concepts Proposal},

Added: sandbox/committee/exceptions/Makefile
==============================================================================
--- (empty file)
+++ sandbox/committee/exceptions/Makefile 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -0,0 +1,4 @@
+d3051.html: deprecating-exception-specs.rst
+ rst2html.py --footnote-references=superscript \
+ --stylesheet-path=./rst.css --embed-stylesheet deprecating-exception-specs.rst \
+ d3051.html

Added: sandbox/committee/exceptions/d3051.html
==============================================================================
--- (empty file)
+++ sandbox/committee/exceptions/d3051.html 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -0,0 +1,648 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />
+<title>Deprecating Exception Specifications</title>
+<meta name="author" content="Doug Gregor" />
+<meta name="date" content="2010-03-10" />
+<style type="text/css">
+
+/*
+:Author: David Goodger
+:Contact: goodger_at_[hidden]
+:Date: $Date: 2006-05-21 16:44:42 -0400 (Sun, 21 May 2006) $
+:Revision: $Revision: 4564 $
+:Copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+
+See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
+customize this style sheet.
+*/
+
+/* used to remove borders from tables and images */
+.borderless, table.borderless td, table.borderless th {
+ border: 0 }
+
+table.borderless td, table.borderless th {
+ /* Override padding for "table.docutils td" with "! important".
+ The right padding separates the table cells. */
+ padding: 0 0.5em 0 0 ! important }
+
+.first {
+ /* Override more specific margin styles with "! important". */
+ margin-top: 0 ! important }
+
+.last, .with-subtitle {
+ margin-bottom: 0 ! important }
+
+.hidden {
+ display: none }
+
+a.toc-backref {
+ text-decoration: none ;
+ color: black }
+
+blockquote.epigraph {
+ margin: 2em 5em ; }
+
+dl.docutils dd {
+ /* margin-bottom: 0.5em */
+ margin: 0 0 0 22px; }
+
+/* Uncomment (and remove this text!) to get bold-faced definition list terms*/
+dl.docutils dt {
+ font-weight: bold;
+ margin: 2em 0 0 22px;
+ line-height: 1.8em;
+ }
+
+
+div.abstract {
+ margin: 2em 5em }
+
+div.abstract p.topic-title {
+ font-weight: bold ;
+ text-align: center }
+
+div.admonition, div.attention, div.caution, div.danger, div.error,
+div.hint, div.important, div.note, div.tip, div.warning {
+ margin: 2em ;
+ border: medium outset ;
+ padding: 1em }
+
+div.admonition p.admonition-title, div.hint p.admonition-title,
+div.important p.admonition-title, div.note p.admonition-title,
+div.tip p.admonition-title {
+ font-weight: bold ;
+ font-family: sans-serif }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title {
+ color: red ;
+ font-weight: bold ;
+ font-family: sans-serif }
+
+/* Uncomment (and remove this text!) to get reduced vertical space in
+ compound paragraphs.
+div.compound .compound-first, div.compound .compound-middle {
+ margin-bottom: 0.5em }
+
+div.compound .compound-last, div.compound .compound-middle {
+ margin-top: 0.5em }
+*/
+
+div.dedication {
+ margin: 2em 5em ;
+ text-align: center ;
+ font-style: italic }
+
+div.dedication p.topic-title {
+ font-weight: bold ;
+ font-style: normal }
+
+div.figure {
+ margin-left: 2em ;
+ margin-right: 2em }
+
+div.footer, div.header {
+ clear: both;
+ font-size: smaller }
+
+div.line-block {
+ display: block ;
+ margin-top: 1em ;
+ margin-bottom: 1em;
+ margin-left: 22px; }
+
+div.line-block div.line-block {
+ margin-top: 0 ;
+ margin-bottom: 0 ;
+ /* margin-left: 1.5em; */
+ margin-left: 22px; }
+
+div.sidebar {
+ margin-left: 1em ;
+ border: medium outset ;
+ padding: 1em ;
+ background-color: #ffffee ;
+ width: 40% ;
+ float: right ;
+ clear: right }
+
+div.sidebar p.rubric {
+ font-family: sans-serif ;
+ font-size: medium }
+
+div.system-messages {
+ margin: 5em }
+
+div.system-messages h1 {
+ color: red }
+
+div.system-message {
+ border: medium outset ;
+ padding: 1em }
+
+div.system-message p.system-message-title {
+ color: red ;
+ font-weight: bold }
+
+div.topic {
+ margin: 2em }
+
+h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
+h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
+ margin-top: 0.4em }
+
+h1.title {
+ text-align: center }
+
+h2.subtitle {
+ text-align: center }
+
+hr.docutils {
+ width: 75% }
+
+img.align-left {
+ clear: left }
+
+img.align-right {
+ clear: right }
+
+ol.simple, ul.simple {
+ margin-bottom: 1em }
+
+ol.arabic {
+ list-style: decimal }
+
+ol.loweralpha {
+ list-style: lower-alpha }
+
+ol.upperalpha {
+ list-style: upper-alpha }
+
+ol.lowerroman {
+ list-style: lower-roman }
+
+ol.upperroman {
+ list-style: upper-roman }
+
+p.attribution {
+ text-align: right ;
+ margin-left: 50% }
+
+p.caption {
+ font-style: italic }
+
+p.credits {
+ font-style: italic ;
+ font-size: smaller }
+
+p.label {
+ white-space: nowrap }
+
+p.rubric {
+ font-weight: bold ;
+ font-size: larger ;
+ color: maroon ;
+ text-align: center }
+
+p.sidebar-title {
+ font-family: sans-serif ;
+ font-weight: bold ;
+ font-size: larger }
+
+p.sidebar-subtitle {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+p.topic-title {
+ font-weight: bold }
+
+pre.address {
+ margin-bottom: 0 ;
+ margin-top: 0 ;
+ font-family: serif ;
+ font-size: 100% }
+
+pre.literal-block, pre.doctest-block {
+ margin-left: 2em ;
+ margin-right: 2em }
+
+span.classifier {
+ font-family: sans-serif ;
+ font-style: oblique }
+
+span.classifier-delimiter {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+span.interpreted {
+ font-family: sans-serif }
+
+span.option {
+ white-space: nowrap }
+
+span.pre {
+ white-space: pre }
+
+span.problematic {
+ color: red }
+
+span.section-subtitle {
+ /* font-size relative to parent (h1..h6 element) */
+ font-size: 80% }
+
+table.citation {
+ border-left: solid 1px gray;
+ margin-left: 1px }
+
+table.docinfo {
+ margin: 2em 4em }
+
+table.docutils {
+ /*margin-top: 0.5em ;
+ margin-bottom: 0.5em;*/
+ margin: 0 0 0 22px; }
+
+table.footnote {
+ border-left: solid 1px black;
+ margin-left: 1px }
+
+table.docutils td, table.docutils th,
+table.docinfo td, table.docinfo th {
+ padding-left: 0.5em ;
+ padding-right: 0.5em ;
+ vertical-align: top }
+
+table.docutils th.field-name, table.docinfo th.docinfo-name {
+ font-weight: bold ;
+ text-align: left ;
+ white-space: nowrap ;
+ padding-left: 0 }
+
+h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
+h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
+ font-size: 100% }
+
+ul.auto-toc {
+ list-style-type: none }
+
+.ins {background-color:#A0FFA0;text-decoration:underline}
+.del {background-color:#FFA0A0;text-decoration:line-through}
+.ed {background-color:#FFFF00}
+
+.grammar { padding: 0 }
+
+.sub {
+ position: relative;
+ bottom: -0.5em;
+ font-size: 0.8em;
+}
+
+</style>
+</head>
+<body>
+<div class="document" id="deprecating-exception-specifications">
+<h1 class="title">Deprecating Exception Specifications</h1>
+<table class="docinfo" frame="void" rules="none">
+<col class="docinfo-name" />
+<col class="docinfo-content" />
+<tbody valign="top">
+<tr><th class="docinfo-name">Author:</th>
+<td>Doug Gregor</td></tr>
+<tr><th class="docinfo-name">Contact:</th>
+<td><a class="first last reference external" href="mailto:doug.gregor@gmail.com">doug.gregor@gmail.com</a></td></tr>
+<tr><th class="docinfo-name">Date:</th>
+<td>2010-03-10</td></tr>
+<tr class="field"><th class="docinfo-name">Number:</th><td class="field-body">D3051=10-0041</td>
+</tr>
+</tbody>
+</table>
+
+<div class="contents topic" id="index">
+index
+<ul class="simple">
+<li><a class="reference internal" href="#introduction" id="id4">Introduction</a></li>
+<li><a class="reference internal" href="#proposed-changes-to-standard-wording" id="id5">Proposed Changes to Standard Wording</a><ul>
+<li><a class="reference internal" href="#dynamic-storage-duration-basic-stc-dynamic" id="id6">3.7.4 Dynamic storage duration [basic.stc.dynamic]</a></li>
+<li><a class="reference internal" href="#exception-specifications-except-spec" id="id7">15.4 Exception specifications [except.spec]</a></li>
+<li><a class="reference internal" href="#d-5-dynamic-exception-specifications-depr-except-spec-dynamic" id="id8">D.5 Dynamic exception specifications [depr.except.spec.dynamic]</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<div class="section" id="introduction">
+<h1><a class="toc-backref" href="#id4">Introduction</a></h1>
+<dl class="docutils">
+<dt>UK-136</dt>
+<dd>Exception specifications have proven close to worthless in practice, while adding a measurable overhead to programs. The feature should be deprecated. The one exception to the rule is the empty throw specification which could serve a legitimate optimizing role if the requirement to call the runtime unexpected mechanism was relaxed in this case.</dd>
+</dl>
+As expressed in the national body comment above, exception
+specifications have not proven useful in practice. There are numerous
+discussions of the problems with exception specifications in C++ (see,
+e.g., <a class="citation-reference" href="#sutter02" id="id1">[Sutter02]</a>, <a class="citation-reference" href="#boost03" id="id2">[Boost03]</a>), but the main issues are:
+<ul class="simple">
+<li>Run-time checking: C++ exception specifications are checked at runtime
+rather than at compile time, so they offer no programmer guarantees
+that all exceptions have been handled. The run-time failure mode
+(calling <tt class="docutils literal">std::unexpected()</tt>) does not lend itself to recovery.</li>
+<li>Run-time overhead: Run-time checking requires the compiler to
+produce additional code that also hampers optimizations.</li>
+<li>Unusable in generic code: Within generic code, it is not generally
+possible to know what types of exceptions may be thrown from
+operations on template arguments, so a precise exception
+specification cannot be written.</li>
+</ul>
+In practice, only two forms of exception-throwing guarantees are
+useful: an operation might throw an exception (any exception) or an
+operation will never throw any exception. The former is expressed by
+omitting the exception-specification entirely, while the latter can be
+expressed as <tt class="docutils literal">throw()</tt> but rarely is, due to performance
+considerations.
+<a class="citation-reference" href="#n3050" id="id3">[N3050]</a> introduces a new kind of exception specification, <tt class="docutils literal">noexcept</tt>,
+the specifies that the function will not throw any exceptions. Unlike
+<tt class="docutils literal">throw()</tt>, <tt class="docutils literal">noexcept</tt> does not require the compiler to introduce
+code to check whether an exception is thrown. Rather, if a function
+specified as <tt class="docutils literal">noexcept</tt> is exited via an exception, the result is
+undefined behavior, which permits compilers to optimize based on the
+knowledge that a <tt class="docutils literal">noexcept</tt> function will not propagate an
+exception.
+With the introduction of <tt class="docutils literal">noexcept</tt>, programmers can now express the
+two kinds of exception guarantees that are useful in practice, without
+additional overhead. This paper therefore proposes to deprecate
+"dynamic" exception specifications, i.e., those based on
+<tt class="docutils literal">noexcept</tt>.
+</div>
+<div class="section" id="proposed-changes-to-standard-wording">
+<h1><a class="toc-backref" href="#id5">Proposed Changes to Standard Wording</a></h1>
+The wording in this paper is based on the current working paper
+(N3035) as amended by N3050.
+<div class="section" id="dynamic-storage-duration-basic-stc-dynamic">
+<h2><a class="toc-backref" href="#id6">3.7.4 Dynamic storage duration [basic.stc.dynamic]</a></h2>
+Modify paragraph 2 as follows:
+<blockquote>
+2 The library provides default definitions for the global allocation
+and deallocation functions. Some global allocation and deallocation
+functions are replaceable (18.6.1). A C++ program shall provide at
+most one definition of a replaceable allocation or deallocation
+function. Any such function definition replaces the default version
+provided in the library (17.6.3.6). The following allocation and
+deallocation functions (18.6) are implicitly declared in global
+scope in each translation unit of a program.
+<pre class="literal-block">
+void* operator new(std::size_t) throw(std::bad_alloc);
+void* operator new[](std::size_t) throw(std::bad_alloc);
+void operator delete(void*) throw() noexcept;
+void operator delete[](void*) throw() noexcept;
+</pre>
+These implicit declarations introduce only the function names
+<tt class="docutils literal">operator new</tt>, <tt class="docutils literal">operator new[]</tt>, <tt class="docutils literal">operator delete</tt>,
+<tt class="docutils literal">operator delete[]</tt> [Note: the implicit declarations do not
+introduce the names <tt class="docutils literal">std</tt> , std::bad_alloc, and
+<tt class="docutils literal">std::size_t</tt>, or any other names that the
+library uses to declare these names. Thus, a new-expression,
+delete-expression or function call that refers to one of these
+functions without including the header <tt class="docutils literal"><new></tt> is
+well-formed. However, referring to <tt class="docutils literal">std</tt> , std::bad_alloc, and
+<tt class="docutils literal">std::size_t</tt> is ill-formed unless the name has been declared by
+including the appropriate header. -- end note] Allocation and/or
+deallocation functions can also be declared and defined for any
+class (12.5).
+</blockquote>
+</div>
+<div class="section" id="exception-specifications-except-spec">
+<h2><a class="toc-backref" href="#id7">15.4 Exception specifications [except.spec]</a></h2>
+Modify the paragraphs in this section as follows. Note that every
+paragraph in this section is accounted for (even those that have not
+changed), to ease review. Editorial notes are [Yellow] and will
+describe, e.g., when specific paragraphs have been moved.
+<blockquote>
+1 A function declaration lists exceptions that its function might
+directly or indirectly throw by using an exception-specification
+as a suffix of its declarator.
+A function is said to allow an
+exception of type <code>E</code> if such an exception will propagate
+from the outermost block of that function out of the function.
+<pre class="literal-block">
+exception-specification:
+ dynamic-exception-specification
+ noexcept-specification
+
+[Moved to D.5p1] dynamic-exception-specification:
+ <code>throw (</code> type-id-listopt <code>)</code>
+
+[Moved to D.5p1] type-id-list:
+ type-id <code>...</code>opt
+ type-id-list <code>,</code> type-id <code>...</code>opt
+
+noexcept-specification:
+ <tt class="docutils literal">noexcept (</tt> constant-expression <tt class="docutils literal">)</tt>
+ <tt class="docutils literal">noexcept</tt>
+</pre>
+In a noexcept-specification, the constant-expression, if supplied,
+shall be a constant expression ([expr.const]) that is contextually
+converted to <tt class="docutils literal">bool</tt> ([conv] Clause 4). A noexcept-specification
+<tt class="docutils literal">noexcept</tt> is equivalent to <tt class="docutils literal">noexcept(true)</tt>.
+2 An exception-specification shall appear only on a function
+declarator for a function type, pointer to function type, reference
+to function type, or pointer to member function type that is the
+top-level type of a declaration or definition, or on such a type
+appearing as a parameter or return type in a function declarator. An
+exception-specification shall not appear in a typedef declaration
+or alias-declaration. [ Example :
+<pre class="literal-block">
+void f() throw(int)noexcept; // OK
+void (*fp)() throw (int)noexcept; // OK
+void g(void pfa() throw(int))noexcept; // OK
+typedef int (*pf)() throw(int)noexcept; // ill-formed
+</pre>
+<ul class="simple">
+<li>end example ]</li>
+</ul>
+[Moved to D.5p2] A type denoted in an exception-specification shall not
+denote an incomplete type. A type denoted in an
+exception-specification shall not denote a pointer or reference to an
+incomplete type, other than void*, const void*, volatile void*, or
+const volatile void*.
+3 If any declaration of a function has an exception-specification,
+all declarations, including the definition and an explicit
+specialization, of that function shall have an
+exception-specification with the same set of type-id s.
+[FIXME: Note about what it means to have the same set of type-ids?]
+If any declaration of a pointer to function, reference to function, or
+pointer to member function has an exception-specification, all
+occurrences of that declaration shall have an
+exception-specification with the same set of type-id s. In an
+explicit instantiation an exception-specification may be specified,
+but is not required. If an exception-specification is specified in
+an explicit instantiation directive, it shall have the same set of
+type-id s as other declarations of that function. A diagnostic is
+required only if the sets of type-id s are different within a single
+translation unit.
+4 [FIXME: Figure out what to do with p4!]
+5 [FIXME: Figure out what to do with p5!]
+6 [Moved to D.5p3] An
+exception-specification can include the same type more than
+once and can include classes that are related by inheritance, even
+though doing so is redundant. [ Note: An
+exception-specification can also include the class
+<code>std::bad_exception</code> (18.8.2.1). - end note
+]
+7 [Moved to D.5p4] A function is
+said to allow an exception of type <code>E</code> if its
+dynamic-exception-specification contains a type
+<code>T</code> for which a handler of type <code>T</code> would be a
+match (15.3) for an exception of type <code>E</code>.
+8 [Moved to D.5p5] Whenever an
+exception is thrown and the search for a handler (15.3) encounters
+the outermost block of a function with an exception-specification,
+the function <code>std::unexpected()</code> is called (15.5.2) if
+the exception-specification does not allow the exception. [
+Example:
+<pre class="literal-block">
+class X { };
+class Y { };
+class Z: public X { };
+class W { };
+
+void f() throw (X, Y) {
+ int n = 0;
+ if (n) throw X(); // OK
+ if (n) throw Z(); // also OK
+ throw W(); // will call std::unexpected()
+}
+</pre>
+-- end example]
+9 [Moved to D.5p6] The function
+<code>std::unexpected()</code> may throw an exception that will
+satisfy the dynamic-exception-specification for which it
+was invoked, and in this case the search for another handler will
+continue at the call of the function with this
+dynamic-exception-specification (see 15.5.2), or it may call
+<code>std::terminate()</code>.
+10 [FIXME: Figure out what to do with p10!]
+11 A function with no exception-specification, or with an
+exception-specification of the form <tt class="docutils literal">noexcept(</tt>
+constant-expression <tt class="docutils literal">)</tt> where the constant-expression yields
+<tt class="docutils literal">false</tt>, allows all exceptions. An exception-specification is
+non-throwing if it is of the form throw(), <tt class="docutils literal">noexcept</tt>,
+or <tt class="docutils literal">noexcept(</tt> constant-expression <tt class="docutils literal">)</tt> where the
+constant-expression yields <tt class="docutils literal">true</tt>
+, or <code>throw()</code> (D.5)
+. A function with a
+non-throwing exception-specification does not allow any
+exceptions.
+12 An exception-specification is not considered part of a function's
+type.
+13 [FIXME: Figure out what to do with p13!]
+14 [Moved to D.5p7] In a dynamic-exception-specification, a type-id followed by an ellipsis is a pack expansion (14.6.3).
+15 [FIXME: Figure out what to do with p15! It's unfortunate
+that we're describing noexcept in terms of throw()]
+</blockquote>
+</div>
+<div class="section" id="d-5-dynamic-exception-specifications-depr-except-spec-dynamic">
+<h2><a class="toc-backref" href="#id8">D.5 Dynamic exception specifications [depr.except.spec.dynamic]</a></h2>
+Insert this new section. Green underlined text is used to
+indicate new wording, while normal text is used whenever text was
+moved from another section (15.4, 15.5).
+<blockquote>
+1 A dynamic exception specification lists exceptions that its function
+might directly or indirectly throw.
+<pre class="literal-block">
+[Moved from 15.4p1] dynamic-exception-specification:
+ <code>throw (</code> type-id-listopt <code>)</code>
+
+[Moved from 15.4p1] type-id-list:
+ type-id <code>...</code>opt
+ type-id-list <code>,</code> type-id <code>...</code>opt
+</pre>
+2 [Moved from 15.4p2] A type denoted in a
+dynamic-exception-specification shall not denote an
+incomplete type. A type denoted in a
+dynamic-exception-specification shall not denote a pointer or
+reference to an incomplete type, other than <code>void*</code>,
+<code>const void*</code>, <code>volatile void*</code>, or
+<code>const volatile void*</code>.
+3 [Moved from 15.4p6] A
+dynamic-exception-specification can include the same type more than
+once and can include classes that are related by inheritance, even
+though doing so is redundant. [ Note: A
+dynamic-exception-specification can also include the class
+<code>std::bad_exception</code> (18.8.2.1). - end note
+]
+4 [Moved from 15.4p7] A function is
+said to allowallows an exception of type <code>E</code> if its
+dynamic-exception-specification contains a type
+<code>T</code> for which a handler of type <code>T</code> would be a
+match (15.3) for an exception of type <code>E</code>.
+5 [Moved from 15.4p8] Whenever an
+exception is thrown and the search for a handler (15.3) encounters
+the outermost block of a function with an
+dynamic-exception-specification, the function
+<code>std::unexpected()</code> is called (15.5.2) if the
+dynamic-exception-specification does not allow the exception. [
+Example:
+<pre class="literal-block">
+class X { };
+class Y { };
+class Z: public X { };
+class W { };
+
+void f() throw (X, Y) {
+ int n = 0;
+ if (n) throw X(); // OK
+ if (n) throw Z(); // also OK
+ throw W(); // will call std::unexpected()
+}
+</pre>
+-- end example]
+6 [Moved from 15.4p9] The function
+<code>std::unexpected()</code> may throw an exception that will
+satisfy the dynamic-exception-specification for which it
+was invoked, and in this case the search for another handler will
+continue at the call of the function with this
+dynamic-exception-specification (see 15.5.2), or it may call
+<code>std::terminate()</code>.
+7 [Moved from 15.4p14] In a dynamic-exception-specification, a type-id followed by an ellipsis is a pack expansion (14.6.3).
+</blockquote>
+<hr class="docutils" />
+Other notes:
+<blockquote>
+15.4p8 needs to refer to dynamic-exception-specification!
+15.4p9 needs the same.</blockquote>
+<hr class="docutils" />
+<table class="docutils citation" frame="void" id="sutter02" rules="none">
+<colgroup><col class="label" /><col /></colgroup>
+<tbody valign="top">
+<tr><td class="label"><a class="fn-backref" href="#id1">[Sutter02]</a></td><td>A Pragmatic Look at Exception Specifications. <a class="reference external" href="http://www.gotw.ca/publications/mill22.htm">http://www.gotw.ca/publications/mill22.htm></td></tr>
+</tbody>
+</table>
+<table class="docutils citation" frame="void" id="boost03" rules="none">
+<colgroup><col class="label" /><col /></colgroup>
+<tbody valign="top">
+<tr><td class="label"><a class="fn-backref" href="#id2">[Boost03]</a></td><td><a class="reference external" href="http://www.boost.org/development/requirements.html#Exception-specification">http://www.boost.org/development/requirements.html#Exception-specification></td></tr>
+</tbody>
+</table>
+<table class="docutils citation" frame="void" id="n3050" rules="none">
+<colgroup><col class="label" /><col /></colgroup>
+<tbody valign="top">
+<tr><td class="label"><a class="fn-backref" href="#id3">[N3050]</a></td><td><ol class="first last upperalpha simple" start="4">
+<li>Abrahams, R. Sharoni, and D. Gregor. Allowing Move Constructors to Throw. Document number N3050=10-0040, ISO C++ Committee Post-Pittsburgh Mailing, March, 2010.</li>
+</ol>
+</td></tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</body>
+</html>

Added: sandbox/committee/exceptions/deprecating-exception-specs.rst
==============================================================================
--- (empty file)
+++ sandbox/committee/exceptions/deprecating-exception-specs.rst 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -0,0 +1,362 @@
+======================================
+ Deprecating Exception Specifications
+======================================
+
+:Author: Doug Gregor
+:Contact: doug.gregor_at_[hidden]
+:date: 2010-03-10
+
+:Number: D3051=10-0041
+
+.. build HTML with:
+
+ rst2html.py --footnote-references=superscript \
+ --stylesheet-path=./rst.css --embed-stylesheet throwing-move.rst \
+ N3051.html
+
+.. contents:: index
+
+Introduction
+************
+
+UK-136
+ Exception specifications have proven close to worthless in practice, while adding a measurable overhead to programs. The feature should be deprecated. The one exception to the rule is the empty throw specification which could serve a legitimate optimizing role if the requirement to call the runtime unexpected mechanism was relaxed in this case.
+
+As expressed in the national body comment above, exception
+specifications have not proven useful in practice. There are numerous
+discussions of the problems with exception specifications in C++ (see,
+e.g., [Sutter02]_, [Boost03]_), but the main issues are:
+
+* *Run-time checking*: C++ exception specifications are checked at runtime
+ rather than at compile time, so they offer no programmer guarantees
+ that all exceptions have been handled. The run-time failure mode
+ (calling ``std::unexpected()``) does not lend itself to recovery.
+* *Run-time overhead*: Run-time checking requires the compiler to
+ produce additional code that also hampers optimizations.
+* *Unusable in generic code*: Within generic code, it is not generally
+ possible to know what types of exceptions may be thrown from
+ operations on template arguments, so a precise exception
+ specification cannot be written.
+
+In practice, only two forms of exception-throwing guarantees are
+useful: an operation might throw an exception (any exception) or an
+operation will never throw any exception. The former is expressed by
+omitting the exception-specification entirely, while the latter *can* be
+expressed as ``throw()`` but rarely is, due to performance
+considerations.
+
+[N3050]_ introduces a new kind of exception specification, ``noexcept``,
+the specifies that the function will not throw any exceptions. Unlike
+``throw()``, ``noexcept`` does not require the compiler to introduce
+code to check whether an exception is thrown. Rather, if a function
+specified as ``noexcept`` is exited via an exception, the result is
+undefined behavior, which permits compilers to optimize based on the
+knowledge that a ``noexcept`` function will not propagate an
+exception.
+
+With the introduction of ``noexcept``, programmers can now express the
+two kinds of exception guarantees that are useful in practice, without
+additional overhead. This paper therefore proposes to deprecate
+"dynamic" exception specifications, i.e., those based on
+``noexcept``.
+
+Proposed Changes to Standard Wording
+************************************
+
+.. role:: sub
+
+.. role:: ins
+
+.. role:: del
+
+.. role:: ed
+
+.. role:: insc(ins)
+ :class: ins code
+
+.. role:: delc(del)
+ :class: ins code
+
+.. role:: raw-html(raw)
+ :format: html
+
+The wording in this paper is based on the current working paper
+(N3035) as amended by N3050.
+
+3.7.4 Dynamic storage duration [basic.stc.dynamic]
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Modify paragraph 2 as follows:
+
+ 2 The library provides default definitions for the global allocation
+ and deallocation functions. Some global allocation and deallocation
+ functions are replaceable (18.6.1). A C++ program shall provide at
+ most one definition of a replaceable allocation or deallocation
+ function. Any such function definition replaces the default version
+ provided in the library (17.6.3.6). The following allocation and
+ deallocation functions (18.6) are implicitly declared in global
+ scope in each translation unit of a program.
+
+ .. parsed-literal::
+
+ void* operator new(std::size_t) :del:`throw(std::bad_alloc)`;
+ void* operator new[](std::size_t) :del:`throw(std::bad_alloc)`;
+ void operator delete(void*) :del:`throw()` :ins:`noexcept`;
+ void operator delete[](void*) :del:`throw()` :ins:`noexcept`;
+
+ These implicit declarations introduce only the function names
+ ``operator new``, ``operator new[]``, ``operator delete``,
+ ``operator delete[]`` [*Note*: the implicit declarations do not
+ introduce the names ``std`` :del:`, std::bad_alloc,` and
+ ``std::size_t``, or any other names that the
+ library uses to declare these names. Thus, a *new-expression*,
+ *delete-expression* or function call that refers to one of these
+ functions without including the header ``<new>`` is
+ well-formed. However, referring to ``std`` :del:`, std::bad_alloc,` and
+ ``std::size_t`` is ill-formed unless the name has been declared by
+ including the appropriate header. -- *end note*] Allocation and/or
+ deallocation functions can also be declared and defined for any
+ class (12.5).
+
+15.4 Exception specifications [except.spec]
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Modify the paragraphs in this section as follows. Note that every
+paragraph in this section is accounted for (even those that have not
+changed), to ease review. Editorial notes are :ed:`[Yellow]` and will
+describe, e.g., when specific paragraphs have been moved.
+
+ 1 A function declaration lists exceptions that its function might
+ directly or indirectly throw by using an *exception-specification*
+ as a suffix of its declarator.
+ :raw-html:`A function is said to allow an
+ exception of type <code>E</code> if such an exception will propagate
+ from the outermost block of that function out of the function.`
+
+ .. parsed-literal::
+
+ *exception-specification*:
+ *dynamic-exception-specification*
+ *noexcept-specification*
+
+ :ed:`[Moved to D.5p1]` :raw-html:`dynamic-exception-specification:`
+ :raw-html:`<code>throw (</code> type-id-listopt <code>)</code>`
+
+ :ed:`[Moved to D.5p1]` :raw-html:`type-id-list:`
+ :raw-html:`type-id <code>...</code>opt`
+ :raw-html:`type-id-list <code>,</code> type-id <code>...</code>opt`
+
+ *noexcept-specification*:
+ ``noexcept (`` *constant-expression* ``)``
+ ``noexcept``
+
+ In a *noexcept-specification*, the *constant-expression*, if supplied,
+ shall be a constant expression ([expr.const]) that is contextually
+ converted to ``bool`` ([conv] Clause 4). A *noexcept-specification*
+ ``noexcept`` is equivalent to ``noexcept(true)``.
+
+ 2 An *exception-specification* shall appear only on a function
+ declarator for a function type, pointer to function type, reference
+ to function type, or pointer to member function type that is the
+ top-level type of a declaration or definition, or on such a type
+ appearing as a parameter or return type in a function declarator. An
+ *exception-specification* shall not appear in a typedef declaration
+ or *alias-declaration*. [ *Example* :
+
+ .. parsed-literal::
+
+ void f() :del:`throw(int)`:ins:`noexcept`; // OK
+ void (\*fp)() :del:`throw (int)`:ins:`noexcept`; // OK
+ void g(void pfa() :del:`throw(int))`:ins:`noexcept`; // OK
+ typedef int (\*pf)() :del:`throw(int)`:ins:`noexcept`; // ill-formed
+
+ - *end example* ]
+
+ :ed:`[Moved to D.5p2]` :del:`A type denoted in an exception-specification shall not
+ denote an incomplete type. A type denoted in an
+ exception-specification shall not denote a pointer or reference to an
+ incomplete type, other than void\*, const void\*, volatile void\*, or
+ const volatile void\*.`
+
+ 3 If any declaration of a function has an *exception-specification*,
+ all declarations, including the definition and an explicit
+ specialization, of that function shall have an
+ *exception-specification* with the same set of *type-id* s.
+ :ed:`[FIXME: Note about what it means to have the same set of type-ids?]`
+ If any declaration of a pointer to function, reference to function, or
+ pointer to member function has an *exception-specification*, all
+ occurrences of that declaration shall have an
+ *exception-specification* with the same set of *type-id* s. In an
+ explicit instantiation an *exception-specification* may be specified,
+ but is not required. If an *exception-specification* is specified in
+ an explicit instantiation directive, it shall have the same set of
+ *type-id* s as other declarations of that function. A diagnostic is
+ required only if the sets of *type-id* s are different within a single
+ translation unit.
+
+ 4 :ed:`[FIXME: Figure out what to do with p4!]`
+
+ 5 :ed:`[FIXME: Figure out what to do with p5!]`
+
+ 6 :ed:`[Moved to D.5p3]` :raw-html:`An
+ exception-specification can include the same type more than
+ once and can include classes that are related by inheritance, even
+ though doing so is redundant. [ Note: An
+ exception-specification can also include the class
+ <code>std::bad_exception</code> (18.8.2.1). - end note
+ ]`
+
+ 7 :ed:`[Moved to D.5p4]` :raw-html:`A function is
+ said to allow an exception of type <code>E</code> if its
+ dynamic-exception-specification contains a type
+ <code>T</code> for which a handler of type <code>T</code> would be a
+ match (15.3) for an exception of type <code>E</code>.`
+
+ 8 :ed:`[Moved to D.5p5]` :raw-html:`Whenever an
+ exception is thrown and the search for a handler (15.3) encounters
+ the outermost block of a function with an exception-specification,
+ the function <code>std::unexpected()</code> is called (15.5.2) if
+ the exception-specification does not allow the exception. [
+ Example:`
+
+ .. parsed-literal::
+
+ :del:`class X { };`
+ :del:`class Y { };`
+ :del:`class Z: public X { };`
+ :del:`class W { };`
+
+ :del:`void f() throw (X, Y) {`
+ :del:`int n = 0;`
+ :del:`if (n) throw X(); // OK`
+ :del:`if (n) throw Z(); // also OK`
+ :del:`throw W(); // will call std::unexpected()`
+ :del:`}`
+
+ :raw-html:`-- end example]`
+
+ 9 :ed:`[Moved to D.5p6]` :raw-html:`The function
+ <code>std::unexpected()</code> may throw an exception that will
+ satisfy the dynamic-exception-specification for which it
+ was invoked, and in this case the search for another handler will
+ continue at the call of the function with this
+ dynamic-exception-specification (see 15.5.2), or it may call
+ <code>std::terminate()</code>.`
+
+ 10 :ed:`[FIXME: Figure out what to do with p10!]`
+
+ 11 A function with no *exception-specification*, or with an
+ *exception-specification* of the form ``noexcept(``
+ *constant-expression* ``)`` where the *constant-expression* yields
+ ``false``, allows all exceptions. An *exception-specification* is
+ non-throwing if it is of the form :del:`throw(),` ``noexcept``,
+ :del:`or` ``noexcept(`` *constant-expression* ``)`` where the
+ *constant-expression* yields ``true``
+ :raw-html:`, or <code>throw()</code> (D.5)`
+ . A function with a
+ non-throwing *exception-specification* does not allow any
+ exceptions.
+
+ 12 An *exception-specification* is not considered part of a function's
+ type.
+
+ 13 :ed:`[FIXME: Figure out what to do with p13!]`
+
+ 14 :ed:`[Moved to D.5p7]` :raw-html:`In a dynamic-exception-specification, a type-id followed by an ellipsis is a pack expansion (14.6.3).`
+
+ 15 :ed:`[FIXME: Figure out what to do with p15! It's unfortunate
+ that we're describing noexcept in terms of throw()]`
+
+:ins:`D.5 Dynamic exception specifications [depr.except.spec.dynamic]`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Insert this new section. :ins:`Green underlined text` is used to
+indicate new wording, while normal text is used whenever text was
+moved from another section (15.4, 15.5).
+
+ 1 :ins:`A dynamic exception specification lists exceptions that its function
+ might directly or indirectly throw.`
+
+ .. parsed-literal::
+
+ :ed:`[Moved from 15.4p1]` :raw-html:`dynamic-exception-specification:`
+ :raw-html:`<code>throw (</code> type-id-listopt <code>)</code>`
+
+ :ed:`[Moved from 15.4p1]` :raw-html:`type-id-list:`
+ :raw-html:`type-id <code>...</code>opt`
+ :raw-html:`type-id-list <code>,</code> type-id <code>...</code>opt`
+
+ 2 :ed:`[Moved from 15.4p2]` :raw-html:`A type denoted in a
+ dynamic-exception-specification shall not denote an
+ incomplete type. A type denoted in a
+ dynamic-exception-specification shall not denote a pointer or
+ reference to an incomplete type, other than <code>void*</code>,
+ <code>const void*</code>, <code>volatile void*</code>, or
+ <code>const volatile void*</code>.`
+
+ 3 :ed:`[Moved from 15.4p6]` :raw-html:`A
+ dynamic-exception-specification can include the same type more than
+ once and can include classes that are related by inheritance, even
+ though doing so is redundant. [ Note: A
+ dynamic-exception-specification can also include the class
+ <code>std::bad_exception</code> (18.8.2.1). - end note
+ ]`
+
+ 4 :ed:`[Moved from 15.4p7]` :raw-html:`A function is
+ said to allowallows an exception of type <code>E</code> if its
+ dynamic-exception-specification contains a type
+ <code>T</code> for which a handler of type <code>T</code> would be a
+ match (15.3) for an exception of type <code>E</code>.`
+
+ 5 :ed:`[Moved from 15.4p8]` :raw-html:`Whenever an
+ exception is thrown and the search for a handler (15.3) encounters
+ the outermost block of a function with an
+ dynamic-exception-specification, the function
+ <code>std::unexpected()</code> is called (15.5.2) if the
+ dynamic-exception-specification does not allow the exception. [
+ Example:`
+
+ .. parsed-literal::
+
+ class X { };
+ class Y { };
+ class Z: public X { };
+ class W { };
+
+ void f() throw (X, Y) {
+ int n = 0;
+ if (n) throw X(); // OK
+ if (n) throw Z(); // also OK
+ throw W(); // will call std::unexpected()
+ }
+
+ :raw-html:`-- end example]`
+
+ 6 :ed:`[Moved from 15.4p9]` :raw-html:`The function
+ <code>std::unexpected()</code> may throw an exception that will
+ satisfy the dynamic-exception-specification for which it
+ was invoked, and in this case the search for another handler will
+ continue at the call of the function with this
+ dynamic-exception-specification (see 15.5.2), or it may call
+ <code>std::terminate()</code>.`
+
+ 7 :ed:`[Moved from 15.4p14]` :raw-html:`In a dynamic-exception-specification, a type-id followed by an ellipsis is a pack expansion (14.6.3).`
+
+
+
+
+------
+
+Other notes:
+
+
+ 15.4p8 needs to refer to dynamic-exception-specification!
+ 15.4p9 needs the same.
+
+------
+
+.. [Sutter02] A Pragmatic Look at Exception Specifications. http://www.gotw.ca/publications/mill22.htm
+
+.. [Boost03] http://www.boost.org/development/requirements.html#Exception-specification
+
+.. [N3050] D. Abrahams, R. Sharoni, and D. Gregor. *Allowing Move Constructors to Throw*. Document number N3050=10-0040, ISO C++ Committee Post-Pittsburgh Mailing, March, 2010.
\ No newline at end of file

Added: sandbox/committee/exceptions/rst.css
==============================================================================
--- (empty file)
+++ sandbox/committee/exceptions/rst.css 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -0,0 +1,294 @@
+/*
+:Author: David Goodger
+:Contact: goodger_at_[hidden]
+:Date: $Date: 2006-05-21 16:44:42 -0400 (Sun, 21 May 2006) $
+:Revision: $Revision: 4564 $
+:Copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+
+See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
+customize this style sheet.
+*/
+
+/* used to remove borders from tables and images */
+.borderless, table.borderless td, table.borderless th {
+ border: 0 }
+
+table.borderless td, table.borderless th {
+ /* Override padding for "table.docutils td" with "! important".
+ The right padding separates the table cells. */
+ padding: 0 0.5em 0 0 ! important }
+
+.first {
+ /* Override more specific margin styles with "! important". */
+ margin-top: 0 ! important }
+
+.last, .with-subtitle {
+ margin-bottom: 0 ! important }
+
+.hidden {
+ display: none }
+
+a.toc-backref {
+ text-decoration: none ;
+ color: black }
+
+blockquote.epigraph {
+ margin: 2em 5em ; }
+
+dl.docutils dd {
+ /* margin-bottom: 0.5em */
+ margin: 0 0 0 22px; }
+
+/* Uncomment (and remove this text!) to get bold-faced definition list terms*/
+dl.docutils dt {
+ font-weight: bold;
+ margin: 2em 0 0 22px;
+ line-height: 1.8em;
+ }
+
+
+div.abstract {
+ margin: 2em 5em }
+
+div.abstract p.topic-title {
+ font-weight: bold ;
+ text-align: center }
+
+div.admonition, div.attention, div.caution, div.danger, div.error,
+div.hint, div.important, div.note, div.tip, div.warning {
+ margin: 2em ;
+ border: medium outset ;
+ padding: 1em }
+
+div.admonition p.admonition-title, div.hint p.admonition-title,
+div.important p.admonition-title, div.note p.admonition-title,
+div.tip p.admonition-title {
+ font-weight: bold ;
+ font-family: sans-serif }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title {
+ color: red ;
+ font-weight: bold ;
+ font-family: sans-serif }
+
+/* Uncomment (and remove this text!) to get reduced vertical space in
+ compound paragraphs.
+div.compound .compound-first, div.compound .compound-middle {
+ margin-bottom: 0.5em }
+
+div.compound .compound-last, div.compound .compound-middle {
+ margin-top: 0.5em }
+*/
+
+div.dedication {
+ margin: 2em 5em ;
+ text-align: center ;
+ font-style: italic }
+
+div.dedication p.topic-title {
+ font-weight: bold ;
+ font-style: normal }
+
+div.figure {
+ margin-left: 2em ;
+ margin-right: 2em }
+
+div.footer, div.header {
+ clear: both;
+ font-size: smaller }
+
+div.line-block {
+ display: block ;
+ margin-top: 1em ;
+ margin-bottom: 1em;
+ margin-left: 22px; }
+
+div.line-block div.line-block {
+ margin-top: 0 ;
+ margin-bottom: 0 ;
+ /* margin-left: 1.5em; */
+ margin-left: 22px; }
+
+div.sidebar {
+ margin-left: 1em ;
+ border: medium outset ;
+ padding: 1em ;
+ background-color: #ffffee ;
+ width: 40% ;
+ float: right ;
+ clear: right }
+
+div.sidebar p.rubric {
+ font-family: sans-serif ;
+ font-size: medium }
+
+div.system-messages {
+ margin: 5em }
+
+div.system-messages h1 {
+ color: red }
+
+div.system-message {
+ border: medium outset ;
+ padding: 1em }
+
+div.system-message p.system-message-title {
+ color: red ;
+ font-weight: bold }
+
+div.topic {
+ margin: 2em }
+
+h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
+h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
+ margin-top: 0.4em }
+
+h1.title {
+ text-align: center }
+
+h2.subtitle {
+ text-align: center }
+
+hr.docutils {
+ width: 75% }
+
+img.align-left {
+ clear: left }
+
+img.align-right {
+ clear: right }
+
+ol.simple, ul.simple {
+ margin-bottom: 1em }
+
+ol.arabic {
+ list-style: decimal }
+
+ol.loweralpha {
+ list-style: lower-alpha }
+
+ol.upperalpha {
+ list-style: upper-alpha }
+
+ol.lowerroman {
+ list-style: lower-roman }
+
+ol.upperroman {
+ list-style: upper-roman }
+
+p.attribution {
+ text-align: right ;
+ margin-left: 50% }
+
+p.caption {
+ font-style: italic }
+
+p.credits {
+ font-style: italic ;
+ font-size: smaller }
+
+p.label {
+ white-space: nowrap }
+
+p.rubric {
+ font-weight: bold ;
+ font-size: larger ;
+ color: maroon ;
+ text-align: center }
+
+p.sidebar-title {
+ font-family: sans-serif ;
+ font-weight: bold ;
+ font-size: larger }
+
+p.sidebar-subtitle {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+p.topic-title {
+ font-weight: bold }
+
+pre.address {
+ margin-bottom: 0 ;
+ margin-top: 0 ;
+ font-family: serif ;
+ font-size: 100% }
+
+pre.literal-block, pre.doctest-block {
+ margin-left: 2em ;
+ margin-right: 2em }
+
+span.classifier {
+ font-family: sans-serif ;
+ font-style: oblique }
+
+span.classifier-delimiter {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+span.interpreted {
+ font-family: sans-serif }
+
+span.option {
+ white-space: nowrap }
+
+span.pre {
+ white-space: pre }
+
+span.problematic {
+ color: red }
+
+span.section-subtitle {
+ /* font-size relative to parent (h1..h6 element) */
+ font-size: 80% }
+
+table.citation {
+ border-left: solid 1px gray;
+ margin-left: 1px }
+
+table.docinfo {
+ margin: 2em 4em }
+
+table.docutils {
+ /*margin-top: 0.5em ;
+ margin-bottom: 0.5em;*/
+ margin: 0 0 0 22px; }
+
+table.footnote {
+ border-left: solid 1px black;
+ margin-left: 1px }
+
+table.docutils td, table.docutils th,
+table.docinfo td, table.docinfo th {
+ padding-left: 0.5em ;
+ padding-right: 0.5em ;
+ vertical-align: top }
+
+table.docutils th.field-name, table.docinfo th.docinfo-name {
+ font-weight: bold ;
+ text-align: left ;
+ white-space: nowrap ;
+ padding-left: 0 }
+
+h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
+h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
+ font-size: 100% }
+
+ul.auto-toc {
+ list-style-type: none }
+
+.ins {background-color:#A0FFA0;text-decoration:underline}
+.del {background-color:#FFA0A0;text-decoration:line-through}
+.ed {background-color:#FFFF00}
+
+.grammar { padding: 0 }
+
+.sub {
+ position: relative;
+ bottom: -0.5em;
+ font-size: 0.8em;
+}

Modified: sandbox/committee/rvalue_ref/throwing-move.rst
==============================================================================
--- sandbox/committee/rvalue_ref/throwing-move.rst (original)
+++ sandbox/committee/rvalue_ref/throwing-move.rst 2010-03-10 21:47:43 EST (Wed, 10 Mar 2010)
@@ -569,7 +569,7 @@
 .. parsed-literal::

 template<class To, class From>
- decltype(static_cast<To>(declval<From>())) convert(From&&) :ins:`noexcept` ;
+ decltype(static_cast<To>(declval<From>())) convert(From&&);

 declares a function template convert, which only participates in overloading if the type From can be explicitly cast to type To. For another example see class template common_type (20.6.7 [meta.trans.other]). - *end example*]

@@ -615,16 +615,16 @@
 - :raw-html:`<code>is_constructible::value</code> is true, where <code>U</code> is <code>remove_all_extents<T>::type.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - :raw-html:`<code>template <class T&gt struct has_copy_constructor;</code>`
- - :raw-html:`<code>T</code> is cv <code>void</code> or <code>is_constructible<U, const U&>::value</code> is true, where <code>U</code> is <code>remove_all_extents<T>::type.`
+ - :raw-html:`<code>is_constructible<U, const U&>::value</code> is true, where <code>U</code> is <code>remove_all_extents<T>::type.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - :raw-html:`<code>template <class T&gt struct has_move_constructor;</code>`
 - :raw-html:`<code>T</code> is cv <code>void</code> or <code>is_constructible<U, U&&>::value</code> is true, where <code>U</code> is <code>remove_all_extents<T>::type.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - :raw-html:`<code>template <class T> struct has_copy_assign;</code></ins>`
- - :raw-html:`<code>T</code> is neither <code>const</code> nor a reference type, and <code>T</code> is a trivial type (3.9) or the expression <code>*(U*)0 = declval<const U&>()</code> is well-formed, where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
+ - :raw-html:`<code>T</code> is neither <code>const</code> nor a reference type, and <code>T</code> is a trivial type (3.9) or the expression <code>*(U*)0 = declval<const U&>()</code> is well-formed when treated as an unevaluated operand (Clause 5), where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - :raw-html:`<code>template <class T> struct has_move_assign;</code></ins>`
- - :raw-html:`<code>T</code> is neither <code>const</code> nor a reference type, and <code>T</code> is a trivial type (3.9) or the expression <code>*(U*)0 = declval()</code> is well-formed, where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
+ - :raw-html:`<code>T</code> is neither <code>const</code> nor a reference type, and <code>T</code> is a trivial type (3.9) or the expression <code>*(U*)0 = declval()</code> is well-formed when treated as an unevaluated operand (Clause 5), where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - ``template <class T> struct has_nothrow_default_constructor;``
 - ``has_trivial_default_constructor<T>::value`` is ``true`` or :raw-html:`<code>T</code> is a class type with a default constructor that is known not to throw any exceptions or <code>T</code> is an array of such a class type<code>is_nothrow_constructible::value</code> is <code>true</code>, where <code>U</code> is <code>remove_all_extents<T>::type</code>`.
@@ -636,10 +636,10 @@
 - :raw-html:`<code>has_trivial_move_constructor<T>::value</code> is <code>true</code> or <code>is_nothrow_constructible<U, U&&>::value</code> is <code>true</code>, where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - ``template <class T> struct has_nothrow_assign;``
- - ``T`` is neither ``const`` nor a reference type, and ``has_trivial_assign<T>::value`` is ``true`` or :raw-html:`<code>T</code> is a class type whose copy assignment operators taking an lvalue of type <code>T</code> are all known not to throw any exceptions or T is an array of such a class type<code>noexcept(*(U*)0 = declval<const U&>())</code> is true, where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
+ - ``T`` is neither ``const`` nor a reference type, and ``has_trivial_assign<T>::value`` is ``true`` or :raw-html:`<code>T</code> is a class type whose copy assignment operators taking an lvalue of type <code>T</code> are all known not to throw any exceptions or T is an array of such a class type<code>noexcept(*(U*)0 = declval<const U&>())</code> is true when treated as an unevaluated operand (Clause 5), where <code>U</code> is <code>remove_all_extents<T>::type</code>.`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`
 * - :raw-html:`<code>template <class T> struct has_nothrow_move_assign;</code>`
- - :raw-html:`<code>has_move_assign<T>::value</code> is true and <code>T</code> is a trivial type (3.9) or the expression <code>noexcept(*(U*)0 = declval())</code> is true, where <code>U</code> is <code>remove_all_extents<T>::type</code>..`
+ - :raw-html:`<code>has_move_assign<T>::value</code> is true and <code>T</code> is a trivial type (3.9) or the expression <code>noexcept(*(U*)0 = declval())</code> is true when treated as an unevaluated operand (Clause 5), where <code>U</code> is <code>remove_all_extents<T>::type</code>..`
 - :raw-html:`<code>T</code> shall be a complete type, (possibly cv-qualified) void, or an array of unknown bound.`

23.3.2.3 deque modifiers [deque.modifiers]

Next message: joel_at_[hidden]: "[Boost-commit] svn:boost r60455 - trunk/libs/spirit/example/scheme"
Previous message: eric_at_[hidden]: "[Boost-commit] svn:boost r60453 - trunk/libs/proto/doc/reference/concepts"

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk