From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: Rob Browning <rlb@defaultvalue.org>
Subject: Re: doco srfi-1 delete, delete-duplicates
Date: Tue, 13 May 2003 13:52:03 +0200 [thread overview]
Message-ID: <xy7llxb6p3w.fsf@nada.kth.se> (raw)
In-Reply-To: <20030513092528.GB28885@www> (tomas@fabula.de's message of "Tue, 13 May 2003 11:25:28 +0200")
tomas@fabula.de writes:
> On Mon, May 12, 2003 at 09:26:58PM -0500, Rob Browning wrote:
>> Kevin Ryde <user42@zip.com.au> writes:
>>
>> > I was sorely tempted to change the "=" formal parameter to something
>> > like "eproc", to avoid any chance of it being confused with the core
>> > "=" procedure. But if that's to be done then I suppose it should be
>> > throughout the chapter, not just in one node.
>>
>> Same temptation here. Perhaps cmp, or comparison, or cmp-func...
>
> Cmp is good (since, as the example shows, it's not just about some
> kind of equality). Pred or predicate might be a candidate as well.
> (but I like cmp best).
...and I think "cmp" is cryptic, arbitrary and ugly, while "=" is
beautiful, and I don't think there is any risk of confusion. I think
the original "=" is good taste. :-)
And if you guys anyway want to change it, please 1. give it a readable
name (e.g. equal-predicate?), and 2. make sure to put a `?' after it
(if it is a textual name) to indicate that it is a predicate.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-13 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 23:50 doco srfi-1 delete, delete-duplicates Kevin Ryde
2003-05-13 2:26 ` Rob Browning
2003-05-13 9:25 ` tomas
2003-05-13 11:52 ` Mikael Djurfeldt [this message]
2003-05-13 13:31 ` tomas
2003-05-13 18:40 ` Mikael Djurfeldt
2003-05-14 8:15 ` tomas
2003-05-15 23:29 ` Kevin Ryde
2003-05-15 23:47 ` Paul Jarc
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xy7llxb6p3w.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--cc=rlb@defaultvalue.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.
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).