Re: Yield should be renamed call_block
- From: John Joyce <dangerwillrobinsondanger@xxxxxxxxx>
- Date: Mon, 9 Jul 2007 12:43:57 +0900
On Jul 8, 2007, at 7:58 PM, Yukihiro Matsumoto wrote:
Hi,to the OP, Of course with your won individual modules/libraries loaded/required, you can alias yield to be whatever isn't already taken by something else. Ideas for aliases: yield_to, call_block, step_out, segway, divert, fork, short_fork, lunch_break, junk_time, call_junk, goto ((hehehe...))
In message "Re: Yield should be renamed call_block"
on Mon, 9 Jul 2007 09:10:23 +0900, Bharat Ruparel <bruparel@xxxxxxxxxxx> writes:
|I find it fascinating and quite a bit true. However, I have to always
|mentally translate the keyword "yeild" to mean "call_block".
The "yield" keyword is used for this purpose from the ages of
languages for example in CLU. So if you learn the history and the
culture, you will find less problem.
I am not going to rename it. But in far future (3.0? maybe), the
keyword will be removed from the language, and you will access blocks
via block arguments of methods.
matz.
John Joyce
.
- Follow-Ups:
- Re: Yield should be renamed call_block
- From: Charles Oliver Nutter
- Re: Yield should be renamed call_block
- From: Chad Perrin
- Re: Yield should be renamed call_block
- References:
- Re: Yield should be renamed call_block
- From: Yukihiro Matsumoto
- Re: Yield should be renamed call_block
- Prev by Date: Re: win32ole: application.quit() leave process running
- Next by Date: Re: why is my program taking so long?
- Previous by thread: Re: Yield should be renamed call_block
- Next by thread: Re: Yield should be renamed call_block
- Index(es):
Relevant Pages
|