From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, 5105@debbugs.gnu.org
Subject: bug#5105: 23.1; doc string of facemenu-set-face
Date: Mon, 01 Aug 2011 20:29:07 -0400 [thread overview]
Message-ID: <jwvr554d5hu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E7FD74EBB7DA4BD3BEE5E0DBBF1F288A@us.oracle.com> (Drew Adams's message of "Mon, 1 Aug 2011 14:47:47 -0700")
>> How 'bout the other way around: give me a reason to accept strings.
> You're the one claiming that there is a good (even _obvious_) reason not to.
> What's the reason, if it's so obvious?
I'm not here to give software engineering courses, sorry.
But if you want, we can start from the very simplest: choice implies
performance and conceptual costs, so unless it's justified by actual
needs it's bad.
So we're back to "why do you think we should also accept strings?".
> And what about faces? Can a given face have two different names? We have
No, but two faces can have the same name.
And there can even be a face which has a unique name and yet `intern'
does not return the corresponding face.
Stefan
next prev parent reply other threads:[~2011-08-02 0:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 16:49 bug#5105: 23.1; doc string of facemenu-set-face Drew Adams
2011-07-13 14:42 ` Lars Magne Ingebrigtsen
2011-07-13 15:39 ` Drew Adams
2011-07-15 16:06 ` Lars Magne Ingebrigtsen
2011-07-15 16:13 ` Drew Adams
2011-07-18 14:27 ` Stefan Monnier
2011-07-18 16:55 ` Drew Adams
2011-08-01 21:27 ` Stefan Monnier
2011-08-01 21:47 ` Drew Adams
2011-08-01 22:21 ` Lars Ingebrigtsen
2011-08-01 22:48 ` Drew Adams
2011-08-02 0:31 ` Stefan Monnier
2011-08-02 0:29 ` Stefan Monnier [this message]
2011-08-02 1:36 ` Drew Adams
2011-08-02 15:42 ` Lars Magne 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
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=jwvr554d5hu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=5105@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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).