unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: Dan Nicolaescu <dann@ics.uci.edu>, emacs-devel@gnu.org
Subject: Re: strange byte compiler behavior
Date: Fri, 04 Jan 2008 01:10:57 -0500	[thread overview]
Message-ID: <jwvwsqqyvfy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1JAf5b-00027Y-P5@fencepost.gnu.org> (Richard Stallman's message of "Fri, 04 Jan 2008 00:27:27 -0500")

> A deeper solution would be to get rid of the boundp test.

> I'm sure it was added for a reason -- there must have been lots of
> spurious warnings without that boundp test.  But nowadays we have done
> a lot to eliminate such warnings with defvars.  Perhaps now if we get
> rid of that boundp test the results would be ok.

> Does someone want to try it?

No need to try: the boundp test is still needed to catch the case of
a variable defined globally in all cases (e.g. in C code or in preloaded
packages) as well as for variables defined in packages that are
`require'd (or loaded transitively by some of the `require'd packages).


        Stefan

  reply	other threads:[~2008-01-04  6:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31 20:55 strange byte compiler behavior Dan Nicolaescu
2007-12-31 21:37 ` martin rudalics
2007-12-31 22:11   ` Dan Nicolaescu
2007-12-31 22:30     ` martin rudalics
2007-12-31 22:42       ` Dan Nicolaescu
2008-01-01 10:33         ` martin rudalics
2008-01-02 19:48 ` Dan Nicolaescu
2008-01-02 21:49   ` martin rudalics
2008-01-02 22:13     ` Dan Nicolaescu
2008-01-02 23:17   ` Dan Nicolaescu
2008-01-02 23:24     ` David Kastrup
2008-01-04  5:27     ` Richard Stallman
2008-01-04  6:10       ` Stefan Monnier [this message]
2008-01-05 14:29         ` Richard Stallman
2008-01-06  2:00           ` Stefan Monnier
2008-01-06 16:34             ` martin rudalics
2008-01-06 18:09             ` Richard Stallman

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=jwvwsqqyvfy.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dann@ics.uci.edu \
    --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).