[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Let's complete by Nov 1, 11:59pm EST
- To: dwheeler@xxxxxxxxxxxx
- Subject: Re: Let's complete by Nov 1, 11:59pm EST
- From: Alan Manuel Gloria <almkglor@xxxxxxxxx>
- Date: Mon, 29 Oct 2012 10:46:12 +0800
- Cc: srfi-105@xxxxxxxxxxxxxxxxx
- Delivered-to: srfi-105@xxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qJHuxvuyPXAwk91bftN0e8XQyyq+37jizrx1TtZL+ko=; b=h5fLrg5jjnpxykC79rhxqWS+OJJCP8xhY1/CCPd6k1F349mH3znOcwpuS8NEso4jjl e7reDqKoL167jbMZ2sy0Z+8DhH/rvd+HIVFE4Ycr3QkBbj9g+YujUJ0OeC1Bm5Vw8ts1 5NVr/6b0XIBjIGj5VEToEg+QelGsogXSb3yBdsGqUThUtSOu9J3UTEKUvkKlB9yrQ+st GVZoeixtn6FYmmKnjUg4Bk6jjGOhzjd5Ji8xICd4D5AVN2PE4JykA7vhT010g9ue8Iuy Qoe+16BiB9f6HoGWc8OhPOvx2WaxT8zf2V2o+6HxbOJQugiYBEqFPRiGT8XhQRxdb20O GgJg==
- In-reply-to: <E1TSdXQ-0008WK-Lq@xxxxxxxxxxxxxxxxx>
- References: <E1TSdXQ-0008WK-Lq@xxxxxxxxxxxxxxxxx>
On 10/29/12, David A. Wheeler <dwheeler@xxxxxxxxxxxx> wrote:
> I cannot imagine accepting a proposal at this point that would change the
> *semantics* of SRFI-105; what's done is done. But I think we should
> entertain fixes in the design rationale (since we want the rationale to be
> right) and typos for just a few more days, and then declare that we're
> done.
>
I was reading through Guile-devel and found this gem by Mark H. Weaver:
http://www.mail-archive.com/guile-devel@xxxxxxx/msg10088.html
Particularly the following exchange between Ludo' (>>) and Mark (>):
>> It’s also unhygienic, in the sense that programs that need it would
>> typically have to start with a definition of $nfx$ & co., although these
>> identifiers never appear literally in the neoteric code.
>
>I agree that this is not ideal, but I see no way around it without
>losing the benefits that these (optional) features are meant to provide.
>
>Apart from the fact that $nfx$ et are meant to be defined by the user,
8<--- snip! read it at the address provided above
The explanation might look good in the design rationale.
Sincerely,
AmkG