From: Pete Becker <petebecker AT acm DOT org>
Newsgroups: comp.os.msdos.djgpp,comp.lang.c++,comp.lang.c
Subject: Re: DJGPP reserves wrong int size
Date: Tue, 26 Jun 2001 21:23:42 -0400
Organization: Dinkumware, Ltd
Lines: 43
Message-ID: <3B39359E.6C27D775@acm.org>
References: <9dde68b7 DOT 0106241053 DOT 2a385311 AT posting DOT google DOT com> <3B36A44F DOT 28AB8846 AT iedu DOT com> <3b37c7a3$0$15028$cc9e4d1f AT news DOT dial DOT pipex DOT com> <3B37D3FF DOT 6FF43454 AT acm DOT org> <2zQZ6.30947$Mf5 DOT 7551891 AT news3 DOT rdc1 DOT on DOT home DOT com> <3B37E46D DOT 18020A4B AT acm DOT org> <hc1ijt06ctcqvtkltu0q5rjcj55nps1r6q AT 4ax DOT com> <3B390AA8 DOT F619524B AT acm DOT org> <mv4ijtgcbdh9qn2r20s38e5hgf3vcd7f5e AT 4ax DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: UmFuZG9tSVbg8PgN4+1n6nH2kbWGUmZnh0/BYKkb2Pc3g30CpHrgcdbrtZTF01OJ
X-Complaints-To: abuse AT rcn DOT com
NNTP-Posting-Date: 27 Jun 2001 01:24:02 GMT
X-Mailer:  Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language:  en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Mark McIntyre wrote:
> 
> On Tue, 26 Jun 2001 18:20:24 -0400, Pete Becker <petebecker AT acm DOT org>
> wrote:
> 
> >Mark McIntyre wrote:
> >>
> >> On Mon, 25 Jun 2001 21:25:01 -0400, Pete Becker <petebecker AT acm DOT org>
> >> wrote:
> >>
> >> >Tom St Denis wrote:
> >> >>
> >> >> "Pete Becker" <petebecker AT acm DOT org> wrote in message
> >> >> news:3B37D3FF DOT 6FF43454 AT acm DOT org...
> >> >> > Stuart Golodetz wrote:
> >> >> > >
> >> >> > > I think the problem is that he cannot read hexadecimal numbers yet he is
> >> >> > > trying to find errors with his compiler's generation of assembly
> >> >> language
> >> >> > > instructions
> >> >> >
> >> >> > Nope. Whether its 18 bytes or 24 bytes the issue is still the same: it's
> >> >> > a great deal more than 4 bytes.
> >> >>
> >> >> So what?  It can reserve 317 bytes if it wants.
> >> >>
> >> >
> >> >Pay attention to context, please. I was responding to the assertion that
> >> >he didn't know what he was talking about because he misread 0x18 as 18.
> >>
> >> and you think that the fact that he can't read hex somehow makes his
> >> other errors ok ?
> >
> >No, and I made no such claim.
> 
> Your posting seems to imply that the MAIN problem is that it reserves
> more than 4 bytes.

Nonsense. Read it again. Or drop this stupid discussion.

-- 
Pete Becker
Dinkumware, Ltd. (http://www.dinkumware.com)