From: Markus Triska <markus.triska@gmx.at>
To: David Kastrup <dak@gnu.org>
Cc: acm@muc.de, Chong Yidong <cyd@stupidchicken.com>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Nonsensical byte compiler warning.
Date: Wed, 04 Apr 2007 11:50:45 +0200 [thread overview]
Message-ID: <877issii2y.fsf@gmx.at> (raw)
In-Reply-To: <86fy7g34tk.fsf@lola.quinscape.zz> (David Kastrup's message of "Wed\, 04 Apr 2007 10\:46\:15 +0200")
David Kastrup <dak@gnu.org> writes:
> I reported this warning without being able to figure out where it
> came from, remember?
Yes, I remember. I also remember that at least 3 other people figured
it out. One of them submitted a patch. Another one couldn't see the
problem despite having pinpointed the exact location of the call (as
you suggest that the optimiser report), believing in a "bug in the
byte compiler". While the error text can be improved, I find it
unjustified to call the current behaviour "nonsensical", "plain
useless" or "a compiler bug". It's a reasonable choice to point to the
enclosing defun, and if your function has dozens of calls to
char-before, there are probably graver problems to worry about.
next prev parent reply other threads:[~2007-04-04 9:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 17:14 Nonsensical byte compiler warning David Kastrup
2007-04-01 18:10 ` Chong Yidong
2007-04-01 20:57 ` Alan Mackenzie
2007-04-02 12:29 ` Richard Stallman
2007-04-04 4:48 ` Markus Triska
2007-04-04 6:15 ` David Kastrup
2007-04-04 8:19 ` Markus Triska
2007-04-04 8:46 ` David Kastrup
2007-04-04 9:50 ` Markus Triska [this message]
2007-04-04 10:17 ` David Kastrup
2007-04-04 12:35 ` Markus Triska
2007-04-04 18:25 ` Markus Triska
2007-04-04 22:13 ` David Kastrup
2007-04-05 6:52 ` Richard Stallman
2007-04-05 7:55 ` Markus Triska
2007-04-06 12:56 ` Richard Stallman
2007-04-06 15:11 ` Chong Yidong
2007-04-08 20:47 ` Markus Triska
2007-04-09 15:42 ` Richard Stallman
2007-04-10 3:53 ` Glenn Morris
2007-04-10 17:27 ` Markus Triska
2007-04-11 4:00 ` Glenn Morris
2007-04-05 18:01 ` Chong Yidong
2007-04-04 20:08 ` Alan Mackenzie
2007-04-04 21:45 ` Markus Triska
2007-04-04 22:11 ` Chong Yidong
2007-04-05 5:44 ` Markus Triska
2007-04-08 1:21 ` Kim F. Storm
2007-04-08 11:27 ` Alan Mackenzie
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=877issii2y.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=acm@muc.de \
--cc=cyd@stupidchicken.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).