-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason Tackaberry wrote: | On Fri, 2008-02-15 at 15:29 +0100, Duncan Webb wrote: |> Actually, I don't see it, but I guess that it blocks some where and |> never returns? | | It will only never return if there's a deadlock (functions A() and B() | are both wait()ing on each other). The main loop is still kept alive in | this case though, but suboptimally, because it's recursed a couple | times. | | (This sort of resource deadlock could still happen with proper async | handling though.) | | |> It's a bit tricky in rel-1 to use the coroutines or callbacks in certain |> places. I really need co-functions. | | What do you mean by cofunctions?
It was a play on words. A (sub)routine or a procedure is a block that doesn't return a result whereas a function does. The use of functions is sometimes can not always be avoided, IMHO they make the code more readable because they show what is purpose of the code block. If I'm understanding this correctly, The problem with callbacks and coroutines is that nothing can be returned so it can be tricky to make the code do what you want. For example, when someone selects a menu item, which in turn needs to make an rpc call and wait for the result which is then used in the menu you need the result before being able to continue. May be I'm missing something obvious. Duncan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHtdQKNi6l+Xvys44RAmSXAJ9cbyR4OtUQdCZvCoNx1rh+PFX6mQCfQ9XD HGaT5gSg7H+SYbrtKMfNApY= =X71k -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
