Mail Archives: djgpp/2001/06/26/13:26:14
"Tom St Denis" <tomstdenis AT yahoo DOT com> wrote in message
news:izRZ6.31082$Mf5 DOT 7689174 AT news3 DOT rdc1 DOT on DOT home DOT com...
>
> "Pete Becker" <petebecker AT acm DOT org> wrote in message
> news:3B37E46D DOT 18020A4B AT acm DOT org...
> > 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.
The issue was not the point I was making, I was saying that perhaps the fact
that he was misreading hex meant he was trying something which was too
difficult for him. As it happens he *can* in fact read hex, as he has kindly
pointed out to me in an email flame, despite the fact that I pointed out I
was not trying to be offensive. Frankly I believe him, and I'm sorry if I
offended him, but whilst his point that I am obviously no good at
programming is probably valid (as I acknowledged in my original post if he'd
actually bothered to read it rather than just flaming me), I'm not convinced
a flame was called for as I was simply trying to help rather than be
offensive. That being said, I'd like to extend a public olive branch of
peace in his general direction so that we can sort this out amicably. I did
not intentionally insult his programming prowess, but if he thinks I did
then I'm sorry. I've no intention of getting into a running flame war with
someone over the size of an integer, it's really not an aspect of my life
that I care overly about to be honest... :o) I'm pretty sure ZMAN doesn't
either...
Oh well, sooner or later, time will tell,
Stuart.
> > >
> > > 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.
>
> Righto, no worries mate.
>
> Tom
>
>
- Raw text -