Re: [Lit.] Buffer overruns
From: Mok-Kong Shen (mok-kong.shen_at_t-online.de)
Date: 12/27/04
- Previous message: Mok-Kong Shen: "Re: [Lit.] Buffer overruns"
- In reply to: Douglas A. Gwyn: "Re: [Lit.] Buffer overruns"
- Next in thread: BRG: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 27 Dec 2004 18:19:36 +0100
Douglas A. Gwyn wrote:
> Mok-Kong Shen wrote:
>
>> And you 'right' kind of safety measure IS?? Have a perfect
>> team of perfect programmers?? (Cf. an earlier post of yours!)
>
>
> I didn't say that. I did say that the main causes of
> buffer overruns are in improper specification/analysis/
> design/coding/documentation/testing/training/management,
> or more briefly, in an inadequate software development
> process, so that is the right place for improvements.
> Also that the notion that some automatic PL feature was
> necessary or sufficient to fix that problem is wrong.
To your last sentence: My view is that some PL features
may 'help' to 'reduce' (not 'eliminate') the probability
of software errors (in general) arising in 'practically'
prevailing (non-ideal) environments of specification/analysis/
design/coding/documentation/testing/training/management. In
(practically unavailable) 'ideal' environments, C or even
assembler (alone) could certainly be just fine.
M. K. Shen
- Previous message: Mok-Kong Shen: "Re: [Lit.] Buffer overruns"
- In reply to: Douglas A. Gwyn: "Re: [Lit.] Buffer overruns"
- Next in thread: BRG: "Re: [Lit.] Buffer overruns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]