Re: [Lit.] Buffer overruns
From: Xcott Craver (caj_at_B-r-a-i-n-H-z.com)
Date: 01/27/05
- Next message: Walter Bushell: "Re: [Lit.] Buffer overruns"
- Previous message: jstevh_at_msn.com: "Math society, weird behavior"
- Maybe in reply to: newstome_at_comcast.net: "Re: [Lit.] Buffer overruns"
- Next in thread: Douglas A. Gwyn: "Re: [Lit.] Buffer overruns"
- Reply: Douglas A. Gwyn: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 27 Jan 2005 01:14:35 GMT
<jmfbahciv@aol.com> wrote:
>
>But what you guys are calling a string, we called an ASCIZ string.
>ASCIZ was the mneumonic that our assembler used to create
>an ASCII string followed by a null.
Well, it wasn't exactly ASCII, because 0x00 is an ASCII
character.
This is what happens when we try to make the same bytes
represent data and metadata. C also has the same philosophy
for functions: little-used data values are returned as error
codes. This has its own set of drawbacks, of course.
-Xcott
- Next message: Walter Bushell: "Re: [Lit.] Buffer overruns"
- Previous message: jstevh_at_msn.com: "Math society, weird behavior"
- Maybe in reply to: newstome_at_comcast.net: "Re: [Lit.] Buffer overruns"
- Next in thread: Douglas A. Gwyn: "Re: [Lit.] Buffer overruns"
- Reply: Douglas A. Gwyn: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|