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

Previous Next

Full log

Message #28 received at 36068 <at> debbugs.gnu.org (full text, mbox):

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

Andreas Schwab <schwab <at> linux-m68k.org> writes:

> On Jun 03 2019, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>>> From: 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-: ?) 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?

It's not.  byte-run--unescaped-character-literals-warning is called from
the byte compiler.  So maybe just let-binding
lread--unescaped-character-literals in byte-compile-from-buffer should
be enough.

Previous Next

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