On Tue, Dec 18, 2012 at 12:31:43PM -0800, Junio C Hamano wrote:
* jk/error-const-return (2012-12-15) 2 commits
- silence some -Wuninitialized false positives
- make error()'s constant return value more visible
Help compilers' flow analysis by making it more explicit that
error() always
Jeff King p...@peff.net writes:
On Tue, Dec 18, 2012 at 12:31:43PM -0800, Junio C Hamano wrote:
* jk/error-const-return (2012-12-15) 2 commits
- silence some -Wuninitialized false positives
- make error()'s constant return value more visible
Help compilers' flow analysis by making it
On Thu, Dec 20, 2012 at 10:13:37AM -0800, Junio C Hamano wrote:
* jk/error-const-return (2012-12-15) 2 commits
- silence some -Wuninitialized false positives
- make error()'s constant return value more visible
Help compilers' flow analysis by making it more explicit that
error()
Jeff King p...@peff.net writes:
So our attempt for more compile-time safety may actually introduce a
run-time bug. And it is a hard bug to find, as the preprocessor
magically converts the error code into -1 without you being able to
see it in the code.
It would be safer to just
Junio C Hamano gits...@pobox.com writes:
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
The tip of the 'master' branch is a bit past 1.8.1-rc2; hopefully we
can go final around the end
5 matches
Mail list logo