From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 31676@debbugs.gnu.org
Subject: bug#31676: 27.0.50; More helpful error message for unescaped character literals
Date: Fri, 19 Apr 2019 11:54:32 +0200 [thread overview]
Message-ID: <CAArVCkSHyEcpaAg_wCwwh8AnHPqRWwOB-jfRi2WbNbdLd24S0w@mail.gmail.com> (raw)
In-Reply-To: <83k1r7sw7m.fsf@gnu.org>
Am Sa., 9. Juni 2018 um 19:31 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Sat, 9 Jun 2018 19:12:30 +0200
> > Cc: larsi@gnus.org, 31676@debbugs.gnu.org
> >
> > Sounds okay, but can you tell why you implemented
> > lread--unescaped-character-literals in C? If that's because you need
> > to call it from load_warn_unescaped_character_literals, then C
> > functions can call Lisp functions with no problems, we have several
> > examples of that in the sources. AFAICT, the C implementation is just
> > a "transliteration" of straightforward Lisp code, so it reads strange.
> >
> > The function uses an uninterned variable, so it has to be in C. I think that's slightly better than interning the
> > variable and having some Lisp function access it (the latter would have one additional internal symbol).
>
> Why does it need an uninterned variable?
It doesn't need to be uninterned, but it's cleaner that way because no
other code can access the variable.
> And if it does, why cannot
> it create a symbol that is not in obarray?
That's what the patch does.
next prev parent reply other threads:[~2019-04-19 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 10:18 bug#31676: 27.0.50; More helpful error message for unescaped character literals Lars Ingebrigtsen
2018-06-02 10:00 ` Philipp Stephani
2018-06-08 14:51 ` Eli Zaretskii
2018-06-09 17:12 ` Philipp Stephani
2018-06-09 17:31 ` Eli Zaretskii
2019-04-19 9:54 ` Philipp Stephani [this message]
2019-04-19 11:43 ` Noam Postavsky
2019-04-19 15:53 ` Philipp Stephani
2019-04-19 16:33 ` Philipp Stephani
2019-04-19 17:22 ` Philipp Stephani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArVCkSHyEcpaAg_wCwwh8AnHPqRWwOB-jfRi2WbNbdLd24S0w@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=31676@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.