public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eerott at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/5461] LONG_LONG_MAX vs LLONG_MAX in range-of-type section of manual Date: Thu, 22 Oct 2009 18:39:00 -0000 [thread overview] Message-ID: <20091022183910.2044.qmail@sourceware.org> (raw) In-Reply-To: <20071209072619.5461.virdiq@gmail.com> ------- Additional Comments From eerott at gmail dot com 2009-10-22 18:39 ------- LONG_LONG_* defines are from the time before C99 standardized to LLONG_* defines. I.e. the current manual seems about 10 years obsolete, I think it's time to refresh it... These obsolete defines are used also elsewhere in the manual, for example here: http://www.gnu.org/s/libc/manual/html_node/Parsing-of-Integers.html Should be trivial to fix with 's/LONG_LONG_/LLONG_/g' on the whole manual. I think this should be pretty safe to do as when I grepped the glibc header files for LONG_LONG_, I got only this: /usr/include/endian.h:# define __LONG_LONG_PAIR(HI, LO) LO, HI /usr/include/endian.h:# define __LONG_LONG_PAIR(HI, LO) HI, LO /usr/include/limits.h:# define LLONG_MAX __LONG_LONG_MAX__ so I don't think there to be any valid instances of LONG_LONG_ in the manual, except maybe in the history section, if it has such... -- What |Removed |Added ---------------------------------------------------------------------------- CC| |eerott at gmail dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5461 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-10-22 18:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-09 7:26 [Bug manual/5461] New: " virdiq at gmail dot com 2009-10-22 18:39 ` eerott at gmail dot com [this message] [not found] <bug-5461-131@http.sourceware.org/bugzilla/> 2012-02-22 21:07 ` [Bug manual/5461] " jsm28 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20091022183910.2044.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).