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 13:54:29 +0200 [thread overview]
Message-ID: <CAAeL0SQxU6ZN3ZNLZd+Dr56ac8YgeVU4orHrW9uuZqSJUS+1vA@mail.gmail.com> (raw)
In-Reply-To: <E402B75AB520498F95966C9FA1688BD1@us.oracle.com>
On Tue, Jun 19, 2012 at 4:45 AM, Drew Adams <drew.adams@oracle.com> wrote:
> Without checking the Common Lisp spec (IANAL), I would guess that even Common
> Lisp, which defines such optimization declarations, leaves it up to CL
> implementations to ignore some of them. But I doubt that it leaves it up to
> them to raise a warning for those declarations it does not recognize.
This is SBCL 1.0.55.7.mswinmt.1185-d20ec0c, an implementation of ANSI
Common Lisp.
;; [etc]
* (defun test1 () (declare (foo)) t)
; in: defun test1
; (FOO)
;
; caught warning:
; unrecognized declaration (foo)
;
; compilation unit finished
; caught 1 WARNING condition
test1
* (defun test2 () (declare (optimize bar)) t)
; in: defun test2
; (OPTIMIZE BAR)
;
; caught warning:
; Ignoring unknown optimization quality bar in: (optimize bar)
;
; compilation unit finished
; caught 1 WARNING condition
test2
*
next prev parent reply other threads:[~2012-06-19 11:54 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 [this message]
2012-06-19 13:34 ` Drew Adams
2012-06-19 13:41 ` Juanma Barranquero
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=CAAeL0SQxU6ZN3ZNLZd+Dr56ac8YgeVU4orHrW9uuZqSJUS+1vA@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.