all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Hackney <dan@haxney.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] Re: package.el changes before the feature freeze
Date: Mon, 08 Oct 2012 10:32:34 +0800	[thread overview]
Message-ID: <87d30tpubh.fsf@gnu.org> (raw)
In-Reply-To: <jwvzk401jk4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 05 Oct 2012 21:38:47 -0400")

> All those make me wonder: do we need the `name' slot to be symbol?
> Why not let it be a string?

Using symbols for package names makes sense conceptually, since a
package name is often the same as the package's library prefix
(e.g. debbugs) or a particular command provided by the library
(e.g. nhexl-mode).  So you'd practically never want to use a package
name that isn't also a good symbol name.  Also, it lets package.el uses
assq rather than assoc in several places, which is always nice.



  reply	other threads:[~2012-10-08  2:32 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 [this message]
2012-10-08 19:16           ` Daniel Hackney
2012-10-08 19:50             ` Stefan Monnier
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=87d30tpubh.fsf@gnu.org \
    --to=cyd@gnu.org \
    --cc=dan@haxney.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.