|
7 | 7 | <section><sref ref="[ostream.formatted.print]"/></section> |
8 | 8 | <submitter>Jan Kokemüller</submitter> |
9 | 9 | <date>13 Jan 2024</date> |
10 | | -<priority>99</priority> |
| 10 | +<priority>4</priority> |
11 | 11 |
|
12 | 12 | <discussion> |
13 | 13 | <p> |
@@ -37,9 +37,19 @@ of the actual output sequence integrity and is therefore set by the second phase |
37 | 37 | Therefore mentioning <tt>ios_base::badbit</tt> in (3.2) doesn't really make sense, it could only meaningfully |
38 | 38 | refer to <tt>ios_base::failbit</tt> instead. |
39 | 39 | </p> |
40 | | -</discussion> |
41 | 40 |
|
42 | | -<resolution> |
| 41 | +<note>2025-10-16; Reflector poll</note> |
| 42 | +<p> |
| 43 | +Set priority to 4 after reflector poll. |
| 44 | +</p> |
| 45 | +<p> |
| 46 | +"NAD. The reason it talks about badbit is that exceptions set badbit in |
| 47 | +IOStreams but not failbit. If we don’t want to hook into the stream’s |
| 48 | +error handling mentioning badbit is correct." |
| 49 | +</p> |
| 50 | + |
| 51 | + |
| 52 | +<superseded> |
43 | 53 | <p> |
44 | 54 | This wording is relative to <paper num="N4971"/>. |
45 | 55 | </p> |
@@ -70,6 +80,47 @@ in the error state of <tt>os</tt>.</p></li> |
70 | 80 | </blockquote> |
71 | 81 | </li> |
72 | 82 | </ol> |
| 83 | +</superseded> |
| 84 | + |
| 85 | +<note>2025-10-16; Daniel provides new wording</note> |
| 86 | + |
| 87 | +</discussion> |
| 88 | + |
| 89 | +<resolution> |
| 90 | + |
| 91 | +<p> |
| 92 | +This wording is relative to <paper num="N5014"/>. |
| 93 | +</p> |
| 94 | + |
| 95 | +<ol> |
| 96 | +<li><p>Modify <sref ref="[ostream.formatted.print]"/> as indicated:</p> |
| 97 | + |
| 98 | +<blockquote> |
| 99 | +<pre> |
| 100 | +void vprint_unicode(ostream& os, string_view fmt, format_args args); |
| 101 | +void vprint_nonunicode(ostream& os, string_view fmt, format_args args); |
| 102 | +</pre> |
| 103 | +<blockquote> |
| 104 | +<p> |
| 105 | +-3- <i>Effects</i>: Behaves as a formatted output function (<sref ref="[ostream.formatted.reqmts]"/>) |
| 106 | +of <tt>os</tt>, except that: |
| 107 | +</p> |
| 108 | +<ol style="list-style-type: none"> |
| 109 | +<li><p>(3.1) — failure to generate output is reported as specified below, and</p></li> |
| 110 | +<li><p>(3.2) — any exception thrown by the call to <tt>vformat</tt> is propagated without regard |
| 111 | +to the value of <tt>os.exceptions()</tt> and without turning on |
| 112 | +<ins><tt>ios_base::failbit</tt> or</ins> |
| 113 | +<tt>ios_base::badbit</tt> |
| 114 | +in the error state of <tt>os</tt>.</p></li> |
| 115 | +</ol> |
| 116 | +<p> |
| 117 | +[…] |
| 118 | +</p> |
| 119 | +</blockquote> |
| 120 | +</blockquote> |
| 121 | +</li> |
| 122 | +</ol> |
| 123 | + |
73 | 124 | </resolution> |
74 | 125 |
|
75 | 126 | </issue> |
0 commit comments