From: Mark McIntyre <mark AT garthorn DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp,comp.lang.c++,comp.lang.c
Subject: Re: DJGPP reserves wrong int size
Date: Wed, 27 Jun 2001 00:01:11 +0100
Message-ID: <mv4ijtgcbdh9qn2r20s38e5hgf3vcd7f5e@4ax.com>
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>
NNTP-Posting-Host: garthorn.demon.co.uk
X-NNTP-Posting-Host: garthorn.demon.co.uk:158.152.83.188
X-Trace: news.demon.co.uk 993596477 nnrp-14:3333 NO-IDENT garthorn.demon.co.uk:158.152.83.188
X-Complaints-To: abuse AT demon DOT net
X-Newsreader: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 39
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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. I'd agree with Stuart that if the Op can't read
Hex, such a problem is a minor one for now ! 
-- 
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>