GNU bug report logs - #36068
27.0.50; Warning: unescaped character literals `?)' detected, `?\)' expected!

Previous Next

Full log

View this message in rfc822 format

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: michael_heerdegen <at> web.de, 36068 <at> debbugs.gnu.org, npostavs <at> gmail.com
Subject: bug#36068: 27.0.50; Warning: unescaped character literals `?)' detected, `?\)' expected!
Date: Mon, 03 Jun 2019 19:04:17 +0200

On Jun 03 2019, Eli Zaretskii <eliz <at> gnu.org> wrote:

>> From: npostavs <at> gmail.com
>> Date: Mon, 03 Jun 2019 09:50:47 -0400
>> Cc: 36068 <at> debbugs.gnu.org, Noam Postavsky <npostavs <at> gmail.com>
>> 
>> Ah, I think the problem can be triggered any time you `read' an unescaped
>> literal outside of `load'.  E.g., from emacs -Q:
>> 
>>     M-: (read "?)") RET
>> 
>> or even just
>> 
>>     M-: ?) RET
>> 
>> Now any byte-compilation will report unescaped `?)'.
>
> Maybe we should forcefully set it to nil at top level?

But how can load_warn_unescaped_character_literals be called while
lread--unescaped-character-literals is not let-bound?

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.