From: David Kastrup <dak@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Why not support (begin), (cond), (case-lambda), etc?
Date: Fri, 06 Jan 2012 10:48:56 +0100 [thread overview]
Message-ID: <871urdyxdj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: CAMMPzYPbawQcg8yeFBm1QArsR2uZyB2MFfKKRmUAj1=nkTvyaA@mail.gmail.com
Alex Shinn <alexshinn@gmail.com> writes:
> On Fri, Jan 6, 2012 at 9:49 AM, Mark H Weaver <mhw@netris.org> wrote:
>>
>> I'd like to argue in favor of supporting (begin), (cond), (case-lambda)
>> and other such degenerate forms, for the same reason that we support
>> (*), (+), and (let () ...).
>>
>> First of all: Is there any compelling reason not to support them?
>> I can't think of one. Can you? If so, please do tell.
>
> 1. portability - these extensions may not work on other
> implementations.
So what?
> 2. the fact that these may be indicators or broken macros.
So may (+).
--
David Kastrup
next prev parent reply other threads:[~2012-01-06 9:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 0:49 Why not support (begin), (cond), (case-lambda), etc? Mark H Weaver
2012-01-06 3:37 ` Alex Shinn
2012-01-06 5:03 ` Mark H Weaver
2012-01-06 6:08 ` Alex Shinn
2012-01-06 8:03 ` Mark H Weaver
2012-01-06 12:08 ` Alex Shinn
2012-01-06 12:26 ` David Kastrup
2012-01-06 12:38 ` Alex Shinn
2012-01-06 12:50 ` David Kastrup
2012-01-06 12:52 ` Alex Shinn
2012-01-06 13:02 ` David Kastrup
2012-01-06 16:13 ` Andy Wingo
2012-01-06 16:19 ` David Kastrup
2012-01-06 17:23 ` Andy Wingo
2012-01-06 17:11 ` Mark H Weaver
2012-05-01 14:10 ` Who moderates the scheme-reports list? Mark H Weaver
2012-05-05 5:09 ` Alex Shinn
2012-05-06 3:36 ` Mark H Weaver
2012-05-06 3:47 ` Alex Shinn
2012-05-06 10:12 ` David Kastrup
2012-05-07 16:26 ` Ludovic Courtès
2012-05-07 17:36 ` Mark H Weaver
2012-05-07 22:06 ` Alex Shinn
2012-05-08 14:42 ` Ludovic Courtès
2012-01-06 9:48 ` David Kastrup [this message]
2012-01-06 9:46 ` Why not support (begin), (cond), (case-lambda), etc? David Kastrup
2012-01-06 16:48 ` Mark H Weaver
2012-01-06 17:02 ` David Kastrup
2012-01-06 16:53 ` Ian Price
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=871urdyxdj.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=guile-devel@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).