From: Hans Aberg <haberg-1@telia.com>
To: Mark H Weaver <mhw@netris.org>
Cc: bug-guile <bug-guile@gnu.org>
Subject: Re: (+ (values 1 2)) should be 1
Date: Wed, 25 May 2011 19:10:56 +0200 [thread overview]
Message-ID: <D24DAEF2-0F6B-44C2-A256-F79031E8252F@telia.com> (raw)
In-Reply-To: <87aaeak9fh.fsf@netris.org>
On 25 May 2011, at 18:54, Mark H Weaver wrote:
>>>> Right, but as the result is unspecified according to the standard, the
>>>> Guile manual suggests that the value SCM_UNSPECIFIED as an
>>>> interpretation of that. I merely say that I think it would be a good
>>>> idea.
>> ...
>>> Having said all this, one could still make the case that we should
>>> attempt to return SCM_UNSPECIFIED from expressions whose values are
>>> unspecified by the standards whenever _practical_. However, doing this
>>> would prevent us from implementing extensions to many aspects of the
>>> standard.
>>
>> Then sec. 10.2.5.2 of the manual needs to be clarified. It should say
>> if a returned value is SCM_UNSPECIFIED then the standard says it is
>> unspecified, but not the other way around.
>
> Okay, I have clarified the description of SCM_UNSPECIFIED.
Fine.
> Thanks for pointing this out.
You are welcome.
Hans
next prev parent reply other threads:[~2011-05-25 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 14:02 (+ (values 1 2)) should be 1 Andy Wingo
2011-05-23 13:34 ` Hans Aberg
2011-05-23 13:49 ` Andy Wingo
2011-05-23 13:58 ` Hans Aberg
2011-05-24 10:35 ` Hans Aberg
2011-05-24 13:11 ` Andy Wingo
2011-05-24 13:48 ` Hans Aberg
2011-05-24 15:07 ` Andy Wingo
2011-05-24 16:13 ` Hans Aberg
2011-05-25 0:25 ` Mark H Weaver
2011-05-25 8:41 ` Hans Aberg
2011-05-25 16:54 ` Mark H Weaver
2011-05-25 17:10 ` Hans Aberg [this message]
2011-06-17 17:43 ` 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=D24DAEF2-0F6B-44C2-A256-F79031E8252F@telia.com \
--to=haberg-1@telia.com \
--cc=bug-guile@gnu.org \
--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).