Re: Why does Ruby have callcc?

< :the previous in number ^ :the list in numerical order > :the next in number P :the previous (in thread) N :the next (in thread) |<:the top of this thread >|:the next thread ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists | :split window (vertically) and show thread lists ~ :close the thread frame .:the index ..:the index of indices

Hi,

In message "Re: Why does Ruby have callcc?"
    on 03/08/07, Mauricio Fern?ndez <batsman.geo / yahoo.com> writes:

|How consistent is this w/ your "no featuritis" policy?  In LL2 you had
|to explain why Ruby had callcc but no macros; your answer was that the
|latter are more easily abused ("too powerful" IIRC).

There's strong reason not to have macros in Ruby, as I believe.
Continuation does not harm you very much.

|Do you still believe that or does "I provide the features, you use them"
|represent a new policy?

I provide the features (which I choose), you use them.

							matz.