From: Richard Dawe Newsgroups: comp.os.msdos.djgpp Subject: Re: size_t Date: Mon, 22 May 2000 21:10:07 +0100 Organization: Customer of Planet Online Lines: 33 Message-ID: <3929941F.C60E027E@bigfoot.com> References: <3923FDDD DOT 2186F25 AT mtu-net DOT ru> <39270C85 DOT BB52285C AT mtu-net DOT ru> <3928150C DOT 8B6BF9CD AT bigfoot DOT com> <392846EF DOT B95361CD AT mtu-net DOT ru> NNTP-Posting-Host: modem-84.iodine.dialup.pol.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: newsg3.svr.pol.co.uk 959105619 19085 62.136.44.84 (23 May 2000 18:13:39 GMT) NNTP-Posting-Date: 23 May 2000 18:13:39 GMT X-Complaints-To: abuse AT theplanet DOT net X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: de,fr To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hello. "Alexei A. Frounze" wrote: > > Richard Dawe wrote: > > > > Hello. > > > > "Alexei A. Frounze" wrote: > > > DO YOU HAVE ANY IDEAS ABOUT THIS (size_t<->fpos_t and other types > > > conversion/casting)??? > > > > The relative sizes will probably be described in the C standard - i.e. > > short is smaller than long, int is the same size as short or bigger, > > or the same size as long or smaller. This should tell you what > > typecasts are safe. > > Actual question was not about type casting in general. It was about type > casting for such things as size_t and fpos_t. Er, it was, unless I don't understand English anymore: "and other types conversion/casting" As I said, the C standard probably has the answer. You mentioned C9X in another posting - this now been ratified as C99. Please read a draft of C99. Bye, -- Richard Dawe richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/