Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!sdcsvax!sdchem!tps
From: tps@sdchem.UUCP
Newsgroups: comp.lang.c
Subject: Re: Standard int sizes
Message-ID: <746@sdchema.sdchem.UUCP>
Date: Tue, 12-May-87 17:57:39 EDT
Article-I.D.: sdchema.746
Posted: Tue May 12 17:57:39 1987
Date-Received: Fri, 15-May-87 05:23:10 EDT
References: <6759@brl-adm.ARPA> <230@ems.UUCP> <170@vianet.UUCP> <764@hoqax.UUCP> <4632@utcsri.UUCP> <761@mcgill-vision.UUCP>
Sender: news@sdchem.UUCP
Reply-To: tps@sdchemf.UUCP (Tom Stockfisch)
Organization: UC San Diego
Lines: 32

In article <761@mcgill-vision.UUCP> mouse@mcgill-vision.UUCP (der Mouse) writes:

>In article <4632@utcsri.UUCP>, flaps@utcsri.UUCP writes:

>> So what that "#define INTPTR int *" doesn't work?  The original
>> author never claimed it did!  "#define int16 int" works fine!

>Until you want to shadow it:
>
>typedef int int16;
>foo()
>{ typedef struct foo int16;
>....
>}
>
>works,

It _should_ work, but it doesn't on BSD
systems.  Typedef identifiers can't be
redefined in a narrower scope.  K&R says
they can, but many, many systems say
they can't.








|| Tom Stockfisch, UCSD Chemistry	tps%chem@sdcsvax.ucsd.edu
					or  sdcsvax!sdchem!tps