> > or have entered a mutex, > > If they're holding a mutex over a function call without a > _really_ good reason, it's their own fault.
Rubbish. It is common to take out a lock in an outer functions and then to call several other functions under the protection of the lock. > > > The alternative is that _every_ function simply return > > a status, which > > > is fundamentally expensive (your real retval has to be > > an out > > > parameter, to start with). Are we talking 'expensive in C' or 'expensive in parrot?' > It is also slow, and speed is priority #1. As far as I'm aware, trading correctness for speed is not an option. -- Alan Burlison -- $ head -1 /dev/bollocks effectively incubate innovative network infrastructures
