Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 May 2012 16:47:52 -0700
From:      "David O'Brien" <obrien@FreeBSD.org>
To:        mdf@FreeBSD.org
Cc:        svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Bruce Evans <brde@optusnet.com.au>
Subject:   Re: svn commit: r235797 - head/contrib/gcc
Message-ID:  <20120523234752.GB22380@dragon.NUXI.org>
In-Reply-To: <CAMBSHm-C7YdU0uPa7aJ6FxDWhZzQiD0_uTj=f1nhV2k5SZ5%2B_A@mail.gmail.com>
References:  <201205221818.q4MII7lk019626@svn.freebsd.org> <20120523050739.H3621@besplex.bde.org> <CAMBSHm-C7YdU0uPa7aJ6FxDWhZzQiD0_uTj=f1nhV2k5SZ5%2B_A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 22, 2012 at 02:07:22PM -0700, mdf@FreeBSD.org wrote:
> We run with the following at Isilon, which is somewhat bogus because
> it allows a bit of sloppiness in types, but is also terribly
> convenient since it means no casting on printf arguments is needed:
... 
> If there's no objections, I (or David or anyone else) can commit to
> the FreeBSD repository.

Unfortunately I don't like this change -- it promotes type sloppiness
that flies in the face of ISO/IEC 9899:1999 (E).

the mixed definition of [u]_?int64_t as it catches improper code -- such
as assuming you can printf an int64_t with "%lld" when that is against
the standard.

-- 
-- David  (obrien@FreeBSD.org)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120523234752.GB22380>