Article View: comp.arch
Article #20814Specifying int size in C
From: 36 more school days
Date: Mon, 17 Apr 1989 20:00
Date: Mon, 17 Apr 1989 20:00
24 lines
1165 bytes
1165 bytes
In 9424 peter@ficc.uu.net (Peter da Silva) sez: >I've suggested this before. I think syntax like: > > int:32 x, y; > int:36 z; /* Unisys 1100 compatibility :-> */ > int a:8, b:9, c:6; int32_t x,y; int16_t c; (and maybe for unsigned) uint16_t n; would probably raise a lot fewer hackles. --chris -- @---@ ----------------------------------------------------------------- @---@ \. ./ | Chris (The Lab Rat) Quenelle cquenel@polyslo.calpoly.edu | \. ./ \ / | All those moments will be lost in time, like tears in rain. | \ / ==o== ----------------------------------------------------------------- ==o==
Technical Details
Message-ID:
<10377@polyslo.CalPoly.EDU>Path:
arc1-ca.pugleaf.net!utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!polyslo!cquenelReferences:
<1032@myrias.UUCP> <12289@reed.UUCP> <16568@winchester.mips.COM> <684@ultb.UUCP> <3879@ficc.uu.net>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!polyslo!cquenel From: cquenel@polyslo.CalPoly.EDU (36 more school days) Newsgroups: comp.arch Subject: Specifying int size in C Message-ID: <10377@polyslo.CalPoly.EDU> Date: 17 Apr 89 20:00:11 GMT References: <1032@myrias.UUCP> <12289@reed.UUCP> <16568@winchester.mips.COM> <684@ultb.UUCP> <3879@ficc.uu.net> Reply-To: cquenel@polyslo.CalPoly.EDU (36 more school days) Organization: Blue Blaze Irregulars Lines: 24