unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: David Kastrup <dak@gnu.org>
Cc: 17296@debbugs.gnu.org
Subject: bug#17296: Uh, wrong?
Date: Mon, 22 Sep 2014 13:34:42 -0400	[thread overview]
Message-ID: <8738bjk18t.fsf@yeeloong.lan> (raw)
In-Reply-To: <87sinku3vj.fsf@yeeloong.lan> (Mark H. Weaver's message of "Wed,  04 Jun 2014 10:49:04 -0400")

Mark H Weaver <mhw@netris.org> writes:

> The fact that the SRFI-1 reference implementation of 'length+' is lax
> very nearly swayed me over to your position, but there's a problem:
> Guile's 'length+' has (always?) returned #f for dotted lists.  It would
> be dangerous to silently change the behavior of this case from one
> non-error to another non-error.  Programs could start silently
> misbehaving without any clue that anything went wrong.

BTW, I looked at the discussion archive for SRFI-1 looking for wisdom
about whether we should eventually make 'length+' lax or not.  I
discovered that Olin Shivers (SRFI-1 author) was in favor of making
essentially all SRFI-1 procedures tolerant of dotted lists, a position
he expressed concisely as "everything is a list", since non-null
non-pairs such as "foo", 2, and even? are naturally regarded as dotted
lists of length 0.

It turns out that he was overwhelming overruled on this.  Some of the
most respected people in the Scheme world agreed it was a bad idea, and
in fact not a single other participant agreed with him.

So he grudgingly changed the spec to reflect the consensus, but he left
his reference implementation as he preferred.

A good summary of the reasons against Olin's preference was given here:

  http://srfi.schemers.org/srfi-1/mail-archive/msg00052.html

If you're curious, here's a threaded index of the entire discussion:

  http://srfi.schemers.org/srfi-1/mail-archive/threads.html

Search for "Everything is a list" for Olin's position, and the threads
following "Re: SRFI-1 round 3 discussion", where Olin tried to defend
his position, then tried to sell a compromise, and finally gave in
completely.

    Regards,
      Mark





      reply	other threads:[~2014-09-22 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 19:26 bug#17296: [PATCH] SRFI-1 'length+' raises an error unless passed a proper or circular list Mark H Weaver
2014-06-02  0:56 ` Mark H Weaver
2014-06-03 17:30 ` bug#17296: Uh, wrong? David Kastrup
2014-06-04  2:55   ` Mark H Weaver
2014-06-04  4:39     ` David Kastrup
2014-06-04 14:49       ` Mark H Weaver
2014-09-22 17:34         ` Mark H Weaver [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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738bjk18t.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=17296@debbugs.gnu.org \
    --cc=dak@gnu.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).