* bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks
[not found] <58232171-11ff-4d19-5107-0e705606d0e8@cs.ucla.edu>
@ 2017-09-24 22:47 ` Paul Eggert
0 siblings, 0 replies; only message in thread
From: Paul Eggert @ 2017-09-24 22:47 UTC (permalink / raw)
To: 27585
[Sending this again since the bug was archived and read-only earlier today.]
-------- Forwarded Message --------
Subject: Re: bug#27585: segfault when evaluating a file containing only backticks
Date: Sun, 24 Sep 2017 11:32:44 -0700
From: Paul Eggert <eggert@cs.ucla.edu>
Philipp Stephani wrote:
> Paul Eggert <eggert@cs.ucla.edu> schrieb am Fr., 14. Juli 2017 um 14:10 Uhr:
>
>> As Eli and Daniel mentioned, this area of Emacs cannot be 100% reliable
>>
>
> Why? Surely Emacs could switch away from recursion for the reader and the
> evaluator to an explicitly-managed stack. That would be a bit of work, but
> certainly not impossible.
You are right, on both points. By "this area of Emacs" I was assuming the
current recursive implementation. It's not the only place Emacs recurses, though.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-09-24 22:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <58232171-11ff-4d19-5107-0e705606d0e8@cs.ucla.edu>
2017-09-24 22:47 ` bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks Paul Eggert
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).