all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: (if (and (featurep 'xemacs) blah) not optimized anymore
Date: Sun, 21 Oct 2007 20:00:55 -0700	[thread overview]
Message-ID: <200710220300.l9M30tGB003742@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <jwvprz8qlem.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun\, 21 Oct 2007 16\:10\:24 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > > Byte compiling this:
  > 
  > > (if (and (featurep 'xemacs) blah)
  > >     (foo))
  > 
  > > with emacs-22.1 does not result in any warning, doing it with the
  > > emacs from trunk results in this:
  > 
  > > In end of data:
  > > foo.el:2:11:Warning: the function `foo' is not known to be defined.
  > 
  > > Any idea what went wrong?
  > 
  > Stupid typo.  Sorry.  Should be fixed now,

Thanks!

Can you please take a look at these:

In end of data:
printing.el:6704:1:Warning: the following functions are not known to
be defined: pr-menu-lookup,
    pr-menu-alist, pr-even-or-odd-pages, pr-menu-get-item,
    pr-menu-set-item-name, pr-menu-lock, pr-menu-set-utility-title,
    pr-menu-set-ps-title, pr-menu-set-txt-title, pr-region-active-p,
    pr-do-update-menus, pr-update-mode-line, pr-f-read-string,
    pr-f-set-keymap-parents, pr-keep-region-active

The functions are defined inside a cond. Is the byte compiler supposed
to deal with that?

  reply	other threads:[~2007-10-22  3:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 16:09 (if (and (featurep 'xemacs) blah) not optimized anymore Dan Nicolaescu
2007-10-21 16:26 ` Richard Stallman
2007-10-21 20:10 ` Stefan Monnier
2007-10-22  3:00   ` Dan Nicolaescu [this message]
2007-10-22  4:58     ` Stefan Monnier
2007-10-22  5:45   ` Dan Nicolaescu
2007-11-13 14:46     ` Stefan Monnier
2007-11-13 16:12       ` Dan Nicolaescu

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=200710220300.l9M30tGB003742@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.