On Friday 06 August 2004 16:58, Bruno Tavares wrote: > Don't take me wrong.. callbacks are great if you have code that fires up > a child and needs to do something when it dies. > But what if you want to fire up 5 childs... but in a sequential way > (meaning the second one can only be fired when the first one terminates, > and if terminates with success)?
Alan Cox' state machine comment applies here ;-) But state machines are admittedly not the way to program IMHO. Auto-generated state machines for parsers are OK, but elsewhere you don't want to have code that implements branching state machines with more than say 5 states. ;-/ OTOH this 5-childs-in-a-row thingy is a bordercase. One _can_ split that code up into different functions (each setting the next as callback) and at least have them be sequentially in the source file. ;-) -- Ciao, / / .o. /--/ ..o / / ANS ooo ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel