all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: 27585@debbugs.gnu.org
Subject: bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks
Date: Sun, 24 Sep 2017 15:47:32 -0700	[thread overview]
Message-ID: <9488bb21-17eb-e13b-fbb0-77089e1d682e@cs.ucla.edu> (raw)
In-Reply-To: <58232171-11ff-4d19-5107-0e705606d0e8@cs.ucla.edu>

[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.





       reply	other threads:[~2017-09-24 22:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58232171-11ff-4d19-5107-0e705606d0e8@cs.ucla.edu>
2017-09-24 22:47 ` Paul Eggert [this message]
2017-09-29  8:32   ` CC'ing archived bugs (was: bug#27585: segfault when evaluating a file containing only backticks) Eli Zaretskii
2017-09-29 19:51     ` CC'ing archived bugs Paul Eggert

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=9488bb21-17eb-e13b-fbb0-77089e1d682e@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=27585@debbugs.gnu.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.