From Jason Turner

[facet.num.get.virtuals]

Diff to HTML by rtfpessoa

tmp/tmpg3ajyqf7/{from.md → to.md} RENAMED
@@ -1,6 +1,6 @@
1
- ##### Virtual functions <a id="facet.num.get.virtuals">[[facet.num.get.virtuals]]</a>
2
 
3
  ``` cpp
4
  iter_type do_get(iter_type in, iter_type end, ios_base& str,
5
  ios_base::iostate& err, long& val) const;
6
  iter_type do_get(iter_type in, iter_type end, ios_base& str,
@@ -25,17 +25,17 @@ iter_type do_get(iter_type in, iter_type end, ios_base& str,
25
 
26
  *Effects:* Reads characters from `in`, interpreting them according to
27
  `str.flags()`, `use_facet<ctype<charT>>(loc)`, and
28
  `use_facet<numpunct<charT>>(loc)`, where `loc` is `str.getloc()`.
29
 
30
- The details of this operation occur in three stages
31
 
32
- - Stage 1: Determine a conversion specifier
33
  - Stage 2: Extract characters from `in` and determine a corresponding
34
  `char` value for the format expected by the conversion specification
35
  determined in stage 1.
36
- - Stage 3: Store results
37
 
38
  The details of the stages are presented below.
39
 
40
  [*Example 1*:
41
 
@@ -85,12 +85,12 @@ Otherwise `false` is stored and `ios_base::failbit` is assigned to
85
 
86
  The `in` iterator is always left pointing one position beyond the last
87
  character successfully matched. If `val` is set, then `err` is set to
88
  `str.goodbit`; or to `str.eofbit` if, when seeking another character to
89
  match, it is found that `(in == end)`. If `val` is not set, then `err`
90
- is set to `str.failbit`; or to `(str.failbit|str.eofbit)` if the reason
91
- for the failure was that `(in == end)`.
92
 
93
  [*Example 2*: For targets `true`: `"a"` and `false`: `"abb"`, the input
94
  sequence `"a"` yields `val == true` and `err == str.eofbit`; the input
95
  sequence `"abc"` yields `err = str.failbit`, with `in` ending at the
96
  `’c’` element. For targets `true`: `"1"` and `false`: `"0"`, the input
 
1
+ ###### Virtual functions <a id="facet.num.get.virtuals">[[facet.num.get.virtuals]]</a>
2
 
3
  ``` cpp
4
  iter_type do_get(iter_type in, iter_type end, ios_base& str,
5
  ios_base::iostate& err, long& val) const;
6
  iter_type do_get(iter_type in, iter_type end, ios_base& str,
 
25
 
26
  *Effects:* Reads characters from `in`, interpreting them according to
27
  `str.flags()`, `use_facet<ctype<charT>>(loc)`, and
28
  `use_facet<numpunct<charT>>(loc)`, where `loc` is `str.getloc()`.
29
 
30
+ The details of this operation occur in three stages:
31
 
32
+ - Stage 1: Determine a conversion specifier.
33
  - Stage 2: Extract characters from `in` and determine a corresponding
34
  `char` value for the format expected by the conversion specification
35
  determined in stage 1.
36
+ - Stage 3: Store results.
37
 
38
  The details of the stages are presented below.
39
 
40
  [*Example 1*:
41
 
 
85
 
86
  The `in` iterator is always left pointing one position beyond the last
87
  character successfully matched. If `val` is set, then `err` is set to
88
  `str.goodbit`; or to `str.eofbit` if, when seeking another character to
89
  match, it is found that `(in == end)`. If `val` is not set, then `err`
90
+ is set to `str.failbit`; or to `(str.failbit | str.eofbit)` if the
91
+ reason for the failure was that `(in == end)`.
92
 
93
  [*Example 2*: For targets `true`: `"a"` and `false`: `"abb"`, the input
94
  sequence `"a"` yields `val == true` and `err == str.eofbit`; the input
95
  sequence `"abc"` yields `err = str.failbit`, with `in` ending at the
96
  `’c’` element. For targets `true`: `"1"` and `false`: `"0"`, the input