From: Stephen Berman <stephen.berman@gmx.net>
To: Glenn Morris <rgm@gnu.org>
Cc: 14565@debbugs.gnu.org
Subject: bug#14565: 24.3.50; Error with byte-compiled function using backward-char
Date: Sat, 08 Jun 2013 15:20:20 +0200 [thread overview]
Message-ID: <87sj0soi23.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <87txlafed4.fsf@rosalinde.fritz.box> (Stephen Berman's message of "Fri, 07 Jun 2013 11:40:23 +0200")
On Fri, 07 Jun 2013 11:40:23 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:
> On Thu, 06 Jun 2013 22:28:22 -0400 Glenn Morris <rgm@gnu.org> wrote:
>
>> I suppose there could still be cases like
>>
>> (setq foo nil)
>> (backward-char foo)
>
> Yes, in fact, after seeing your fix, I realized that I had
> oversimplified my test case; the code which revealed the bug actually
> looks more like this (still simplified, but enough to raise the error
> with your fix):
>
> (defun my-test-3 ()
> (let (x)
> (backward-char (when x 2))))
>
>> I wonder if these bytecomp handlers are worth keeping?
>
> I don't see how to tweak byte-compile-backward-char to account for the
> above cases, but I don't understand the bytecomp code well. However, I
> did test adding a case Bbackward_char to exec_byte_code parallel to
> Bforward_char, and that handles the above cases as expected. So that
> may be the easiest fix.
Should this bug be reopened, or would you prefer me to submit a new
report for the unresolved cases?
Steve Berman
next prev parent reply other threads:[~2013-06-08 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 14:24 bug#14565: 24.3.50; Error with byte-compiled function using backward-char Stephen Berman
2013-06-06 18:30 ` Stephen Berman
2013-06-06 21:05 ` Glenn Morris
2013-06-07 2:28 ` Glenn Morris
2013-06-07 9:40 ` Stephen Berman
2013-06-08 13:20 ` Stephen Berman [this message]
2013-06-08 13:46 ` Stephen Berman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj0soi23.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=14565@debbugs.gnu.org \
--cc=rgm@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 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).