unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: Ian Hulin <ian@hulin.org.uk>, 10099@debbugs.gnu.org
Subject: bug#10099: Null (begin) blocks - V2.0.3 reports error was OK in V2.0.2
Date: Fri, 25 Nov 2011 12:13:39 +0100	[thread overview]
Message-ID: <8739dccv4s.fsf@pobox.com> (raw)
In-Reply-To: <87aa7kqyh9.fsf@fencepost.gnu.org> (David Kastrup's message of "Fri, 25 Nov 2011 11:37:38 +0100")

Hi David,

Thanks for the note, and good to hear from you on the Guile side.  You
are right in pointing out areas that can improve.  As you might imagine,
we are currently more focussed on the current stable 2.0.x and
development 2.2.x series, so we probably won't do very much to the 1.8
documentation, for example.  I understand if you need to keep 1.8
support for a time, but the 2.0 documentation is much better.

I am going to open a new thread for the local-eval issue, if you don't
mind.

On Fri 25 Nov 2011 11:37, David Kastrup <dak@gnu.org> writes:

> (lambda ())
> ((lambda () (begin)))
> ((lambda () (begin (begin))))

FWIW, we are not going to change to support these in any branch of
Guile.  No other Scheme does so, and we mostly take our language design
hints from the Scheme standards.

> I have switched to using *unspecified* and unspecified? by now, but it
> might be worth ironing out the strange behaviors of (begin) nevertheless
> in particular where they conflict with the behavior to be expected from
> the documentation (preferably both in v1.8 as well as v2), in addition
> to mentioning the more straightforward commands.

I'll see what we can do.  I think the decision here is going to depend
on what we do in 2.2 regarding (if #f #f).  In any case, we do need to
improve our documentation.

Andy
-- 
http://wingolog.org/





  reply	other threads:[~2011-11-25 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4ECA89A5.5090202@hulin.org.uk>
2011-11-21 23:02 ` Null (begin) blocks - V2.0.3 reports error was OK in V2.0.2 Andy Wingo
2011-11-25 10:37   ` bug#10099: " David Kastrup
2011-11-25 11:13     ` Andy Wingo [this message]
2011-11-23 12:27 ` Andy Wingo
2011-11-24 23:49   ` Ian Hulin
2011-11-25  9:31     ` Andy Wingo
2011-12-22  1:17   ` Andy Wingo

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=8739dccv4s.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=10099@debbugs.gnu.org \
    --cc=dak@gnu.org \
    --cc=ian@hulin.org.uk \
    /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).