From: "Robert P. J. Day" <rpjday@mindspring.com>
To: C programming list <linux-c-programming@vger.kernel.org>
Subject: the rationale for redefining integral types?
Date: Wed, 3 Aug 2005 07:53:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0508030750250.4376@localhost.localdomain> (raw)
(i apologize if i asked this before once upon a time, i'm sort of
immersed in digging through some legacy code and it's all starting to
merge together.)
in this legacy code, one of the previous authors took it upon
himself to redefine some of the basic integral types, such as int8,
int16, int32 ... that sort of thing.
there doesn't appear to be any benefit to these internally redefined
types over the ones in the standard library, so i can't see why it
would have been done.
is there some reason a programmer might want to do this?
rday
p.s. and, no, there doesn't appear to be anything subtlely clever
about the redefinitions. just plain int and unsigned int of length 8
bits, 16 bits, ... etc.
next reply other threads:[~2005-08-03 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 11:53 Robert P. J. Day [this message]
2005-08-03 12:04 ` the rationale for redefining integral types? Steve Graegert
2005-08-03 12:14 ` Robert P. J. Day
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=Pine.LNX.4.63.0508030750250.4376@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-c-programming@vger.kernel.org \
/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: link
Be 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 NNTP newsgroup(s).