From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14816 invoked by alias); 22 Nov 2009 17:36:07 -0000 Received: (qmail 14766 invoked by uid 48); 22 Nov 2009 17:35:56 -0000 Date: Sun, 22 Nov 2009 17:36:00 -0000 Message-ID: <20091122173556.14765.qmail@sourceware.org> From: "john at johnmaddock dot co dot uk" To: glibc-bugs@sources.redhat.com In-Reply-To: <20091120005823.10990.mateusz@loskot.net> References: <20091120005823.10990.mateusz@loskot.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/10990] Inconsistent definition of int64_t in sys/types and stdint.h X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00133.txt.bz2 ------- Additional Comments From john at johnmaddock dot co dot uk 2009-11-22 17:35 ------- The point here is that stdint.h behaves differently depending upon what has been #included previously, for example: #include // possibly included from some deep dependency #include May *NOT* result in int64_t being defined if __GLIBC_HAVE_LONG_LONG is not set, where as had stdint.h been the first include then it *would* have been defined. In other words stdint.h may not follow the C99 std depending upon what has happened to be included previously. Still think it's not a bug? IMO stdint.h should always define int64_t no matter what other headers may have been included first. John Maddock. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |john at johnmaddock dot co | |dot uk Status|RESOLVED |REOPENED Resolution|INVALID | http://sourceware.org/bugzilla/show_bug.cgi?id=10990 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.