From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: acm@muc.de, Markus Triska <markus.triska@gmx.at>, emacs-devel@gnu.org
Subject: Re: Nonsensical byte compiler warning.
Date: Fri, 06 Apr 2007 11:11:25 -0400 [thread overview]
Message-ID: <873b3dillu.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1HZnzv-0007t3-UT@fencepost.gnu.org> (Richard Stallman's message of "Fri\, 06 Apr 2007 08\:56\:59 -0400")
Richard Stallman <rms@gnu.org> writes:
> Warnings stemming from the optimiser are commonly restricted to
> defun-level positional information. For example, byte compiling:
>
> (defun f ()
> (message "hi")
> (quote 0 1)
> (let ((x 0 1))))
>
> gives two warnings (both to the defun). Should these be fixed too?
>
> I agree this is too hard to change now.
> However, it would have been premature to give up without
> checking.
I've added a TODO item for this:
** Make byte-optimization warnings issue accurate line numbers.
next prev parent reply other threads:[~2007-04-06 15:11 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
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 [this message]
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=873b3dillu.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=markus.triska@gmx.at \
--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).