unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@gnu.org>
Cc: 13052-done@debbugs.gnu.org, 13052@debbugs.gnu.org
Subject: bug#13052: 24.3.50; mention recent change of `kbd' to a function in NEWS
Date: Thu, 6 Dec 2012 10:02:57 -0800	[thread overview]
Message-ID: <886E4E8BD0A044388F5C603215BBE824@us.oracle.com> (raw)
In-Reply-To: <878v9gyfwe.fsf@gnu.org>

> As for the `pure' property, it's now mentioned in the Lisp manual.

It is now mentioned, but this is all the manual says about it:

 This property is used internally to mark certain named functions
 for byte compiler optimization.  Do not set it.

Please explain why it is not appropriate for users to use this property on their
own functions.  That is not clear at all.

Why shouldn't a user function with a definition similar or even identical to
that for `kbd' have `pure' applied to it?  Especially since this apparently
affects only byte-compilation and has nothing to do with pure storage and
dumping Emacs.

What is your reason for declaring this off-limits for programmers of Emacs Lisp?
What good does that do?






      parent reply	other threads:[~2012-12-06 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02  0:28 bug#13052: 24.3.50; mention recent change of `kbd' to a function in NEWS Drew Adams
2012-12-02  1:52 ` Juanma Barranquero
2012-12-02  2:18   ` Drew Adams
2012-12-02  2:26     ` Juanma Barranquero
2012-12-02  3:36       ` Drew Adams
2012-12-02  3:50         ` Juanma Barranquero
2012-12-02  4:07           ` Drew Adams
2012-12-02  4:19             ` Juanma Barranquero
2012-12-02  4:50               ` Drew Adams
2012-12-02 11:33     ` Michael Heerdegen
2012-12-02  9:14 ` Chong Yidong
2012-12-02 17:13   ` Drew Adams
2012-12-06 18:02   ` Drew Adams [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

  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=886E4E8BD0A044388F5C603215BBE824@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13052-done@debbugs.gnu.org \
    --cc=13052@debbugs.gnu.org \
    --cc=cyd@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 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).