tmp/tmpyfynduck/{from.md → to.md}
RENAMED
|
@@ -1,13 +1,13 @@
|
|
| 1 |
## Comments <a id="lex.comment">[[lex.comment]]</a>
|
| 2 |
|
| 3 |
The characters `/*` start a comment, which terminates with the
|
| 4 |
characters `*/`. These comments do not nest. The characters `//` start a
|
| 5 |
-
comment, which terminates
|
| 6 |
-
a form-feed or a vertical-tab character in such a
|
| 7 |
-
white-space characters shall appear between it and the
|
| 8 |
-
terminates the comment; no diagnostic is required. The
|
| 9 |
-
characters `//`, `/*`, and `*/` have no special meaning within a
|
| 10 |
-
comment and are treated just like other characters. Similarly, the
|
| 11 |
comment characters `//` and `/*` have no special meaning within a `/*`
|
| 12 |
comment.
|
| 13 |
|
|
|
|
| 1 |
## Comments <a id="lex.comment">[[lex.comment]]</a>
|
| 2 |
|
| 3 |
The characters `/*` start a comment, which terminates with the
|
| 4 |
characters `*/`. These comments do not nest. The characters `//` start a
|
| 5 |
+
comment, which terminates immediately before the next new-line
|
| 6 |
+
character. If there is a form-feed or a vertical-tab character in such a
|
| 7 |
+
comment, only white-space characters shall appear between it and the
|
| 8 |
+
new-line that terminates the comment; no diagnostic is required. The
|
| 9 |
+
comment characters `//`, `/*`, and `*/` have no special meaning within a
|
| 10 |
+
`//` comment and are treated just like other characters. Similarly, the
|
| 11 |
comment characters `//` and `/*` have no special meaning within a `/*`
|
| 12 |
comment.
|
| 13 |
|