Here are two cases I happened to notice via Coverity. Neither produces a user-visible bug; it's just slightly misleading code which can be cleaned up. The first one is ancient, but since the nearby code changed, Coverity considered it new. :) The second one is actually recent; I noted it already on the list, but it was already in 'next' at that point and is now in 'master'. -Peff
