From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11735@debbugs.gnu.org
Subject: bug#11735: 24.1.50; "Warning: Unknown defun property ... in ..."
Date: Tue, 19 Jun 2012 15:41:11 +0200 [thread overview]
Message-ID: <CAAeL0SS3CCHX6GZ8UXZxaUv=TgTHydEdbB0091cOV20Odz_xcQ@mail.gmail.com> (raw)
In-Reply-To: <ADFD0278F785417EACD7C143D4097C1E@us.oracle.com>
On Tue, Jun 19, 2012 at 3:34 PM, Drew Adams <drew.adams@oracle.com> wrote:
> (Actually, you've shown only that there exists an implementation (albeit a
> common one) that prints a warning. That does not confirm that the CL spec says
> that's OK. But I claimed IANAL...)
http://www.sbcl.org/manual/index.html#ANSI-Conformance
"Essentially every type of non-conformance is considered a bug. (The
exceptions involve internal inconsistencies in the standard.)"
> Perhaps this kind of message is a candidate for a :debug warning level? I
> already said that it is useful for programmers. I do not see it as helpful for
> general users just loading a library. On the contrary: some might become
> confused, if not downright worried. That's all I'm trying to say.
I'm all for ways to silence irrelevant warnings.
Juanma
next prev parent reply other threads:[~2012-06-19 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 17:45 bug#11735: 24.1.50; "Warning: Unknown defun property ... in ..." Drew Adams
2012-06-18 20:37 ` Stefan Monnier
2012-06-18 20:49 ` Drew Adams
2012-06-18 21:11 ` Drew Adams
2012-06-18 21:43 ` Stefan Monnier
2012-06-18 22:03 ` Drew Adams
2012-06-19 0:59 ` Stefan Monnier
2012-06-19 2:45 ` Drew Adams
2012-06-19 11:54 ` Juanma Barranquero
2012-06-19 13:34 ` Drew Adams
2012-06-19 13:41 ` Juanma Barranquero [this message]
2012-06-19 16:36 ` Stefan Monnier
2012-06-19 17:08 ` Drew Adams
2012-06-19 21:37 ` Stefan Monnier
2012-06-19 22:01 ` Drew Adams
2014-02-09 3:40 ` Lars Ingebrigtsen
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='CAAeL0SS3CCHX6GZ8UXZxaUv=TgTHydEdbB0091cOV20Odz_xcQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=11735@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.