From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Hackney <dan@haxney.org>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] Re: package.el changes before the feature freeze
Date: Mon, 08 Oct 2012 15:50:48 -0400 [thread overview]
Message-ID: <jwva9vwsq7f.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAMqXDZvvhNfLpvDXAK5kcWfMTKdZg7Y2mYoF5TSVWEJcmtzrnA@mail.gmail.com> (Daniel Hackney's message of "Mon, 8 Oct 2012 15:16:36 -0400")
> The CL info pages refer to them as slots, so that's what I figured I'd
> use. There could be a better name for a package defstruct, but "field"
> "property" and "attribute" are overdone :)
Sure, use whatever suits you.
> I agree that the slot name could definitely be improved. `name' does
> imply a string to me, but I think that it is good for the "primary key"
> of the alists to be a symbol. Something like `canonical-name' perhaps?
> `id' maybe? I'm not terribly attached to any particular slot name.
`name' is no worse than the others, so just use that.
> This was intended to be related to `define-package'; it turns the
> `define-package' call into a `package-desc' struct.
I understand the motivation, but the use of a "package-" prefix is
more important, I think.
> I haven't looked at lexical binding in earnest. Should I reference
> the non-prefixed form in the body of `define-package'?
The symbols prefixed by "_" are not treated specially by the
compiler/evaluator. The use of _ only affects the warnings you might
get (where a `_foo' that is used or a `foo' that is not used will signal
a warning) and the way things are displayed in *Help* (where the
underscore is stripped, since whether or not an argument is used is an
implementation detail).
Stefan
next prev parent reply other threads:[~2012-10-08 19:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 16:58 package.el changes before the feature freeze Daniel Hackney
2012-09-30 20:21 ` Stefan Monnier
2012-09-30 23:50 ` Daniel Hackney
2012-10-01 1:21 ` Stefan Monnier
2012-10-01 3:11 ` Chong Yidong
2012-10-03 0:33 ` Daniel Hackney
2012-10-03 22:41 ` [PATCH] " Daniel Hackney
2012-10-04 8:16 ` Chong Yidong
2012-10-05 23:13 ` Daniel Hackney
2012-10-06 1:38 ` Stefan Monnier
2012-10-08 2:32 ` Chong Yidong
2012-10-08 19:16 ` Daniel Hackney
2012-10-08 19:50 ` Stefan Monnier [this message]
2012-10-09 1:11 ` Daniel Hackney
2012-10-09 6:48 ` Stefan Monnier
2012-10-09 17:07 ` Daniel Hackney
2012-10-09 17:39 ` Stefan Monnier
2012-10-09 21:39 ` Daniel Hackney
2012-10-09 22:25 ` Glenn Morris
2012-10-12 3:58 ` Chong Yidong
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=jwva9vwsq7f.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@gnu.org \
--cc=dan@haxney.org \
--cc=emacs-devel@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.