In article <20011012141333.E11755@atl.lmco.com>, Chuck Winters <cwinters@atl.lmco.com> writes: > This may be a stupid question, but why does the sock->state > only hold the shift of the state? Why doesn't it just hold > the state so that you don't have to do all the bit shifts in > the code? Read the code again... It contains just the state. The shifts are just a fancy way to test for multiple states efficiently in parallel. -Andi - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
