[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escape
From: |
Alan Mackenzie |
Subject: |
bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escaped. |
Date: |
Wed, 23 Sep 2020 14:48:24 +0000 |
Hello, Mattias.
On Wed, Sep 23, 2020 at 11:01:59 +0200, Mattias EngdegÄrd wrote:
> Sorry if I misunderstood, but since when do backslashes escape */ in C?
Since forever, but only in the CC Mode test suite. :-(
I just tried it out with gcc, and it seems that \*/ does indeed end a
block comment. But an escaped newline doesn't end a line comment,
instead continuing it to the next line. So I got confused. Thanks for
pointing out the mistake.
It seems that as well as the existing variable
comment-end-can-be-escaped, we need a new one, say
line-comment-end-can-be-escaped, too. In C and C++ modes, these would
be nil and t respectively.
--
Alan Mackenzie (Nuremberg, Germany).
- bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escaped., Alan Mackenzie, 2020/09/22
- bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escaped., Mattias EngdegÄrd, 2020/09/23
- bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escaped., Michael Welsh Duggan, 2020/09/24
- bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escaped., Alan Mackenzie, 2020/09/24
- bug#43558: [PATCH]: Fix (forward-comment 1) when end delimiter is escaped., Michael Welsh Duggan, 2020/09/24