all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Engster <deng@randomsample.de>
Cc: "Eric M. Ludlam" <zappo@gnu.org>,
	Stephen Leake <stephen_leake@stephe-leake.org>,
	emacs-devel@gnu.org
Subject: Re: Noisy byte compilation on master
Date: Wed, 18 Feb 2015 17:44:45 -0500	[thread overview]
Message-ID: <jwv8ufu3kov.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871tlnnglj.fsf@engster.org> (David Engster's message of "Wed, 18 Feb 2015 20:51:20 +0100")

>> If you get such warnings at run-time, it's a bug.  They should only
>> appear at byte-compilation time.

> Insert

>   (require 'eieio)
>   (defclass foo () ())
>   (foo "test")

> then do eval-buffer and you'll see

>   Obsolete name arg "test" to constructor foo

That's not a bug.  Because `eval-buffer' is the "byte-compilation time".
For it to count as a bug, you'd have to byte-compile the above code and
get the warning when you run the resulting compiled code.


        Stefan



      reply	other threads:[~2015-02-18 22:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 16:06 Noisy byte compilation on master Eli Zaretskii
2015-02-02 16:31 ` Stefan Monnier
2015-02-02 16:35   ` Eli Zaretskii
2015-02-02 18:01   ` Stephen Leake
2015-02-02 23:23     ` Stefan Monnier
2015-02-03  7:03       ` David Engster
2015-02-04 15:45         ` Stefan Monnier
2015-02-15 15:58           ` David Engster
2015-02-16  2:56             ` Stefan Monnier
2015-02-16 21:11               ` David Engster
2015-02-16 23:14                 ` Stefan Monnier
2015-02-17  6:31                   ` David Engster
2015-02-17 23:06                     ` Stefan Monnier
2015-02-18 17:53                       ` David Engster
2015-02-18 19:35                         ` Stefan Monnier
2015-02-18 19:51                           ` David Engster
2015-02-18 22:44                             ` Stefan Monnier [this message]

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=jwv8ufu3kov.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=deng@randomsample.de \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.org \
    --cc=zappo@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 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.