From:	"Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: size_t
Date:	Mon, 22 May 2000 00:28:31 +0400
Organization:	MTU-Intel ISP
Lines:	22
Message-ID:	<392846EF.B95361CD@mtu-net.ru>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000518173007 DOT 15189B AT is> <3923FDDD DOT 2186F25 AT mtu-net DOT ru> <39270C85 DOT BB52285C AT mtu-net DOT ru> <3928150C DOT 8B6BF9CD AT bigfoot DOT com>
NNTP-Posting-Host:	ppp108-234.dialup.mtu-net.ru
Mime-Version:	1.0
X-Trace:	gavrilo.mtu.ru 958940953 71823 212.188.108.234 (21 May 2000 20:29:13 GMT)
X-Complaints-To:	usenet-abuse AT mtu DOT ru
NNTP-Posting-Date:	21 May 2000 20:29:13 GMT
X-Mailer:	Mozilla 4.72 [en] (Win95; I)
X-Accept-Language:	ru,en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

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.

bye.
Alexei A. Frounze
-----------------------------------------
Homepage: http://alexfru.chat.ru
Mirror:   http://members.xoom.com/alexfru

- Raw text -