Re: Difference between MACRO: and define-transform

Hi,
extra/random.combinators hasn't been merged in. Should I change
something, or just keep it in my work/ directory ?
Jon

On Mon, Aug 23, 2010 at 9:40 PM, Jon Harper <jon.harper87@...> wrote:
> Hi,
> The random.combinators vocabulary (with tests and docs) is ready for review :
> git://github.com/jonenst/factor.git random-combinators
>
> Jon
>
>
>
> On Wed, Aug 18, 2010 at 4:29 AM, Slava Pestov <slava@...> wrote:
>> On Tue, Aug 17, 2010 at 10:20 AM, Jon Harper
<jon.harper87@...> wrote:
>>> Hi,
>>> I looked at the implementation of cond and case, and I saw the
>>> define-transform and "no-compile" word property. How is it different
>>> from the MACRO: construction ? Is user code supposed to use it at all
>>> ?
>>
>> Not really. define-transform lets you have a different definition for
>> the optimized and non-optimized usages of the word, so its only needed
>> for combinators such as 'cond' which are called a lot during
>> bootstrap. In this case you want to avoid generating the quotation
>> every time, so the non-optimized definition is used. For user code
>> which is always optimized, define-transform does not offer any
>> benefits.