Re:Coding tricks I learnt at Apple
by SoftwareMaven on Friday June 10, 2011 @01:12PM
(#2641602)
Not necessarily. It could be a particularly tricky and critical piece of code that they want to ensure nobody is "auto-merging" into oblivion.
By putting a mutex on it, you are forced to re-evaluate the state when you obtain the lock. You can't sneak in a change in front of somebody else's change, requiring them to re-evaluate (or, worse, merge and hope).
If it was required for modules all over, it would be broken process. For a single module, I can understand it.
By putting a mutex on it, you are forced to re-evaluate the state when you obtain the lock. You can't sneak in a change in front of somebody else's change, requiring them to re-evaluate (or, worse, merge and hope).
If it was required for modules all over, it would be broken process. For a single module, I can understand it.