Dan,
It might be nice if we could get rid of 2curry, 3curry, 3compose,
prepose eventually. For example, consider this snippet which uses
2curry twice:
[
[ dup >link where dup ] 2dip
[ >r >r first r> at r> push-at ] 2curry
[ 2drop ]
if
] 2curry each
The fry version is a lot clearer:
'[
dup >link where dup
[ first , at , push-at ] [ 2drop ] if
] each
On Sun, Aug 31, 2008 at 5:03 PM, Daniel Ehrenberg <[EMAIL PROTECTED]> wrote:
> Well, personally, I never got used to fry. I feel comfortable using
> curry and compose for most things. I don't see why it is a problem to
> use them except in exceptionally complicated cases. For me, it feels
> like fry is doing more than is needed. Are you suggesting that we use
>
> { 1 2 3 } 4 '[ , + ] map
>
> in place of
>
> { 1 2 3 } 4 [ + ] curry map
>
> ? I don't understand how that is much of an improvement. I'm not sure
> how to do what "with" does in terms of fry. For building complicated
> quotations, it's another story. It seems like both are useful.
>
> Dan
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
