[Twisted-Python] Re: Synchronization techniques

[Paul G]

Nicola Larosa wrote:
> Paul G wrote:
>> while there are a few languages, like erlang for example, that
>> express event loops with cooperative threading syntax (processes,
>> messages and futures), i'm of the opinion that it's actually harmful
>> to hide the event loop details from people who haven't started
>> thinking that way yet - they should be simply syntactic sugar for
>> when you've already grokked the model.
>
> IIUC, the same holds true for inline callbacks, right?
>
> http://twistedmatrix.com/documents/current/api/twisted.internet.defer.html#inlineCallbacks

nice, haven't seen that yet. it's not quite what i was agitating against - 
you still see an explicit async cutpoint and still have to realize what's 
going on. while i personally wouldn't recommend using this method all 
throughout, it does look to be very useful for situations where you'll never 
need to reuse the bottom half.

-p