From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Philipp Stephani <p.stephani2@gmail.com>
Cc: 25017-done@debbugs.gnu.org
Subject: bug#25017: Fwd: Re: dotimes var comiler warning
Date: Mon, 28 Nov 2016 08:54:13 -0800 (PST) [thread overview]
Message-ID: <2e72cdb4-d73d-4b41-b8d2-ffb47ce7b8c7@default> (raw)
In-Reply-To: <87k2bn1s7e.fsf@web.de>
> > The (implicit) decision to diverge further from Common Lisp has
> > been made a while ago, by prefixing the CL functions with `cl' and
> > importing the `seq' and `map' libraries, which provide similar
> > functionality, but with a different interface.
>
> Maybe (though, I don't think there was such decision, implicit or
> not - "seq" and "map" functions also have an according prefix - I
> wouldn't say we are converging are diverging to/from Common Lisp
> at all, but give developers a stylistic choice). But here were
> are talking about a construct that exists in pure Elisp, and OTOH
> also in Common Lisp, sharing the same name. If there is not
> really a need to make the semantics differ, I prefer to leave
> things as they are, because everything else would probably be
> more confusing than helpful.
+1. Well put.
prev parent reply other threads:[~2016-11-28 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878ts957gj.fsf@web.de>
2016-11-24 14:10 ` bug#25017: Fwd: Re: dotimes var comiler warning Andreas Röhler
2016-11-24 14:23 ` npostavs
2016-11-24 14:35 ` Michael Heerdegen
2016-11-24 14:44 ` Michael Albinus
2016-11-24 16:50 ` Michael Heerdegen
2016-11-24 17:01 ` Michael Heerdegen
2016-11-25 6:03 ` Drew Adams
2016-11-27 10:20 ` Michael Heerdegen
2016-11-27 18:23 ` Drew Adams
2016-11-27 20:11 ` Philipp Stephani
2016-11-28 16:31 ` Michael Heerdegen
2016-11-28 16:54 ` 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=2e72cdb4-d73d-4b41-b8d2-ffb47ce7b8c7@default \
--to=drew.adams@oracle.com \
--cc=25017-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=p.stephani2@gmail.com \
/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).