[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Monkey-patching $quasi-value$

To: srfi-108@xxxxxxxxxxxxxxxxx
Subject: Re: Monkey-patching $quasi-value$
From: Per Bothner <per@xxxxxxxxxxx>
Date: Sun, 25 Nov 2012 00:43:12 -0800
Delivered-to: srfi-108@xxxxxxxxxxxxxxxxx
In-reply-to: <50B1D28B.4070409@xxxxxxxxxxx>
References: <20121124070834.GK1610@xxxxxxxxxxxxxxxx> <50B087DD.4000002@xxxxxxxxxxx> <20121125030714.GL1610@xxxxxxxxxxxxxxxx> <50B1D28B.4070409@xxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2

On 11/25/2012 12:10 AM, Per Bothner wrote:

What do you think of ($construct$:foo ..) instead of the rather
ungainly ($quasi-value-transformer$:foo ...)?


I'm thinking the use of colon may cause some complications (or at
least portability issues), since Kawa does some magic with colons.

How about just plain:

&#foo[...] ==>  ($construct$foo ..)
--
	--Per Bothner
per@xxxxxxxxxxx   http://per.bothner.com/

References:
- Monkey-patching $quasi-value$
  - From: John Cowan
- Re: Monkey-patching $quasi-value$
  - From: Per Bothner
- Re: Monkey-patching $quasi-value$
  - From: John Cowan
- Re: Monkey-patching $quasi-value$
  - From: Per Bothner

Prev by Date: Re: SRFI-108/SRFI-109 special characters
Next by Date: Re: Monkey-patching $quasi-value$
Previous by thread: Re: Monkey-patching $quasi-value$
Next by thread: Re: Monkey-patching $quasi-value$
Index(es):
- Date
- Thread