[Python] Opposite of yield?

	Christos TZOTZIOY Georgiou
	Sep 10, 2003 at 9:03 pm

On Wed, 10 Sep 2003 20:19:35 GMT, rumours say that "Dave Benjamin"
<dave at 3dex.com> might have written:

Perhaps a new Python statement "suck"?

Oh come on, now, just because Java does it...

QOTW +1 :)

--
TZOTZIOY, I speak England very best,
Microsoft Security Alert: the Matrix began as open source.

Search Discussions

Dave Benjamin: "Bob Gailer" wrote in message news:mailman.1063223955.7295.python-list at python.org... Oh come on, now, just because Java does it...

Follow ups

Achrist: That looks good. But that needs a thread to block, right? A generator manages to run without being a thread (at least overtly). If we have the suck() statement, we also need something that's the opposite of a generator (a Sucker?) and something that's the opposite of an iterator (a Suckee?). I'm starting to get an idea why this is completely not all there. The main question this raises is "How lightweight are threads?" Can I program with dozens or hundreds of python threads in a program (for
Achrist: This style supports only output-driven processes. The generator, being on the input side, is always the server, and the output side is always the client. It doesn't fit the situation where the input is heterogeneous and input has to get spewed in several directions, depending on its content. Al
Peter Hansen: The real question might be why would you want to? If you don't want a thread, but you want something which takes input from elsewhere and does some processing, then returns control to some other place until more data is available (which is what one might assume if threads aren't good for you), there is already a convenient solution: the subroutine. ;-) Seriously, what's the requirement driving the need for this? (I suspect Erik Max's answer is still what you need, and you misunderstand the

Discussion Navigation

view	thread \| post
posts	‹ prev \| 6 of 20 \| next ›

Discussion Overview

font	variable	Hotkey: f
user style	avatars	Hotkey: a