tmp/tmphd212qhl/{from.md → to.md}
RENAMED
|
@@ -1,15 +1,16 @@
|
|
| 1 |
### Ambiguity resolution <a id="dcl.ambig.res">[[dcl.ambig.res]]</a>
|
| 2 |
|
| 3 |
The ambiguity arising from the similarity between a function-style cast
|
| 4 |
and a declaration mentioned in [[stmt.ambig]] can also occur in the
|
| 5 |
-
context of a declaration. In that context, the choice is between
|
| 6 |
-
|
| 7 |
-
|
| 8 |
-
|
| 9 |
-
[[stmt.ambig]], the resolution is to consider any
|
| 10 |
-
|
|
|
|
| 11 |
|
| 12 |
[*Note 1*: A declaration can be explicitly disambiguated by adding
|
| 13 |
parentheses around the argument. The ambiguity can be avoided by use of
|
| 14 |
copy-initialization or list-initialization syntax, or by use of a
|
| 15 |
non-function-style cast. — *end note*]
|
|
|
|
| 1 |
### Ambiguity resolution <a id="dcl.ambig.res">[[dcl.ambig.res]]</a>
|
| 2 |
|
| 3 |
The ambiguity arising from the similarity between a function-style cast
|
| 4 |
and a declaration mentioned in [[stmt.ambig]] can also occur in the
|
| 5 |
+
context of a declaration. In that context, the choice is between an
|
| 6 |
+
object declaration with a function-style cast as the initializer and a
|
| 7 |
+
declaration involving a function declarator with a redundant set of
|
| 8 |
+
parentheses around a parameter name. Just as for the ambiguities
|
| 9 |
+
mentioned in [[stmt.ambig]], the resolution is to consider any
|
| 10 |
+
construct, such as the potential parameter declaration, that could
|
| 11 |
+
possibly be a declaration to be a declaration.
|
| 12 |
|
| 13 |
[*Note 1*: A declaration can be explicitly disambiguated by adding
|
| 14 |
parentheses around the argument. The ambiguity can be avoided by use of
|
| 15 |
copy-initialization or list-initialization syntax, or by use of a
|
| 16 |
non-function-style cast. — *end note*]
|