unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Bogus byte-compiler warnings
Date: Sun, 12 Nov 2006 14:27:51 +0100	[thread overview]
Message-ID: <v9slgo4wx4.fsf@marauder.physik.uni-ulm.de> (raw)

Hi,

when byte-compiling the following file
(cf. `gnus-display-time-event-handler' in `gnus-start.el')...

--8<---------------cut here---------------start------------->8---
(defun foo-func-1 ()
  (when (and (boundp 'foo-var)
	     (fboundp 'foo-1))
    (foo-1)))

(defun foo-func-2 ()
  (and (boundp 'foo-var)
       (fboundp 'foo-2)
       (foo-2)))

;; Cf. `gnus-display-time-event-handler' in `gnus-start.el'
--8<---------------cut here---------------end--------------->8---

... I get:

,----
| In end of data:
| rs-byte-compile-warnings.el:11:1:Warning: the function `foo-1' is not known to
|     be defined.
`----

foo-1 will not be called if it's not fbound.  (Emacs complains about
both, foo-1 and foo-2).  Maybe this warning could be avoided (after
the release?).

Does it make sense to change `gnus-display-time-event-handler' in
`gnus-start.el' to the form of `foo-func-2' just to avoid the warning?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

             reply	other threads:[~2006-11-12 13:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12 13:27 Reiner Steib [this message]
2006-11-13  9:44 ` Bogus byte-compiler warnings Richard Stallman
2006-11-13 11:27   ` Reiner Steib
2006-11-16 17:31   ` Chong Yidong
2006-11-16 18:51     ` Davis Herring
2006-11-19  7:59     ` Richard Stallman
2006-11-19 15:18       ` Chong Yidong
2007-12-01 11:29         ` Reiner Steib
2007-12-01 16:47           ` Dan Nicolaescu
2007-12-01 17:33             ` Reiner Steib
     [not found] <E1GjIng-0005ML-HG@monty-python.gnu.org>
2006-11-12 21:47 ` Jonathan Yavner
2006-11-13  0:57   ` Drew Adams

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=v9slgo4wx4.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).