unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: "Marc Nieper-Wißkirchen" <marc.nieper@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>, John Cowan <cowan@ccil.org>,
	guile-devel@gnu.org
Subject: Re: [PATCH] add SRFI: srfi-121; generators
Date: Tue, 04 Aug 2020 19:24:24 +0200	[thread overview]
Message-ID: <87k0yez5mf.fsf@web.de> (raw)
In-Reply-To: <CAEYrNrSiyBct-mveyshzCt5FGOdbvcBO4ABXhvUdGyPeeSYgGw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]


Marc Nieper-Wißkirchen <marc.nieper@gmail.com> writes:
>>> While I have been contributing to R7RS-large, I have to agree with you
>>> to some extent. Most of the SRFIs that have been voted into R7RS-large
>>> or are to be submitted for it don't have the quality of the R6RS or
>>> R7RS(-small) specifications
>
>> Inevitably so.  A large granite boulder cannot be cut like a diamond, but it has uses that a diamond does not (and vice versa, of course).
>
> There's already a large granite boulder called Python. When we want to
> advertise R7RS-large, which differences shall we point out (apart from
> the Lisp syntax)?

What I would like to see is a reduction step at the end. With Python we
have urllib, urllib2 and urllib3. Scheme offers the chance to clean up 

What Scheme brings to the table are multiple implementations for
different use-cases, along with a real standard.

Also first-class macros.

Though that doesn’t mean that letting quality lapse won’t hurt.

Do we actually have to take SRFI without changes into r7rs-large? Isn’t
an advantage of a standard that it can smooth out all those rough edges
you get when you bring together parts that were developed in isolation?

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2020-08-04 17:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.61.1596470427.10776.guile-devel@gnu.org>
2020-08-03 19:41 ` [PATCH] add SRFI: srfi-121; generators Marc Nieper-Wißkirchen
2020-08-04 12:48   ` Marc Nieper-Wißkirchen
2020-08-04 15:24   ` John Cowan
2020-08-04 15:58     ` Marc Nieper-Wißkirchen
2020-08-04 17:24       ` Dr. Arne Babenhauserheide [this message]
2021-01-21 18:39 John Cowan
2021-01-23  0:58 ` Mark H Weaver
2021-01-23  2:14   ` Shiro Kawai
2021-01-23  2:18     ` Arthur A. Gleckler
2021-01-23  6:37       ` Mark H Weaver
2021-01-26  3:29         ` John Cowan
2021-01-26  6:48           ` Linus Björnstam
2021-01-26  6:49             ` Linus Björnstam
2021-01-26  7:14             ` Marc Nieper-Wißkirchen
2021-01-26 11:54               ` Linus Björnstam
2021-04-08 15:53                 ` Arthur A. Gleckler
2021-04-11  6:52                   ` Linus Björnstam
2021-04-11 16:17                     ` Arthur A. Gleckler
  -- strict thread matches above, loose matches on Subject: below --
2020-08-01  3:42 John Cowan
2020-08-02 22:39 ` Mark H Weaver
2019-07-01  0:09 nly
2019-07-01  5:06 ` Mark H Weaver
2019-07-01  6:00   ` Mark H Weaver
2019-07-01  6:21     ` Amar Singh

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=87k0yez5mf.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=cowan@ccil.org \
    --cc=guile-devel@gnu.org \
    --cc=marc.nieper@gmail.com \
    --cc=mhw@netris.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).