>>>>> "DS" == Dan Sugalski <dan@sidhe.org> writes: DS> Not gonna happen. Tk and signals, at the very least, will see to that. DS> Coroutines are also an awfully limited threading mechanism, and I think DS> they'd have the same problems that threads have (or the use of multiple DS> processors in an SMP system would be shot), so it seems silly to limit DS> threading to coroutines. DS> Might as well do 'em all, though the low-level contstructs (i.e. what we DS> build) may overlap a bunch. i *agree* very strongly. a clean low level design will support all the flow methods equally well and with decent efficiency. that is a major reason why i want to move all of those rfc's under the flow one so we can properly address that low level design and language changes to support them all. i should have my draft rfc done later tonight and will post it. it has some missing sections you can fill in like on co-routines and completions. uri -- Uri Guttman --------- uri@sysarch.com ---------- http://www.sysarch.com SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books The Best Search Engine on the Net ---------- http://www.northernlight.comThread Previous | Thread Next