Re: [Lit.] Buffer overruns
From: Brian Inglis (Brian.Inglis_at_SystematicSW.Invalid)
Date: 01/31/05
- Next message: Tom Linden: "Re: [Lit.] Buffer overruns"
- Previous message: Brian Inglis: "Re: [Lit.] Buffer overruns"
- In reply to: Tom Linden: "Re: [Lit.] Buffer overruns"
- Next in thread: Tom Linden: "Re: [Lit.] Buffer overruns"
- Reply: Tom Linden: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 31 Jan 2005 14:43:15 GMT
On Sun, 30 Jan 2005 16:23:07 -0800 in alt.folklore.computers, "Tom
Linden" <tom@kednos.com> wrote:
>On Sun, 30 Jan 2005 18:54:53 GMT, Brian Inglis
><Brian.Inglis@SystematicSW.Invalid> wrote:
>
>> It's the design that does the encapsulation; the implementation just
>> supports that encapsulation of the design.
>> C (or assembler) supports just as much encapsulation as any other
>> language; most languages nowadays are compiled or interpreted by C
>> code, and they all end up as assembler generated or executed.
>
>
>You are mistaken. That is not true for any IBM compilers or for those
>on VMS, and none of these pass through assembly as has been common in
>the Unix world, they generate machine code. In fact none of these are
>even written in C.
For IBM, replace C by PL/S; for VMS, replace C by BLISS; replace
assembler by machine code; same stuff, different representation.
--
Thanks. Take care, Brian Inglis Calgary, Alberta, Canada
Brian.Inglis@CSi.com (Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
fake address use address above to reply
- Next message: Tom Linden: "Re: [Lit.] Buffer overruns"
- Previous message: Brian Inglis: "Re: [Lit.] Buffer overruns"
- In reply to: Tom Linden: "Re: [Lit.] Buffer overruns"
- Next in thread: Tom Linden: "Re: [Lit.] Buffer overruns"
- Reply: Tom Linden: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|