From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Steve Graegert <graegerts@gmail.com>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: Re: the rationale for redefining integral types?
Date: Wed, 3 Aug 2005 08:14:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0508030810120.4744@localhost.localdomain> (raw)
In-Reply-To: <6a00c8d505080305045ad09980@mail.gmail.com>
On Wed, 3 Aug 2005, Steve Graegert wrote:
> On 8/3/05, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > 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.
>
> Sounds weird, indeed, but I suspect the code to be pre-POSIX (before
> 1989).
nope, the code is at most 4 years old.
> > 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.
>
> The only reason I could think of is that the developer wanted to
> introduce some kind of portability by masking underlying types (and
> probably their size) transparently. Is this particular piece of
> code part of a library? Do the headers contain some #ifdefs to
> allow conditional compilation for certain systems?
nope and nope. i'm just going to assume i can replace it with
standard C types. if something breaks, well, then i'll have my
answer, i guess. thanks.
rday
prev parent reply other threads:[~2005-08-03 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 11:53 the rationale for redefining integral types? Robert P. J. Day
2005-08-03 12:04 ` Steve Graegert
2005-08-03 12:14 ` Robert P. J. Day [this message]
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.0508030810120.4744@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=graegerts@gmail.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).