Xref: utzoo comp.sys.ibm.pc:23046 comp.sys.intel:657
Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!vsi1!daver!lynx!m5
From: m5@lynx.uucp (Mike McNally)
Newsgroups: comp.sys.ibm.pc,comp.sys.intel
Subject: Re: unsafe computing (Was: correct code for pointer subtraction)
Keywords: C pointer math runtime errors
Message-ID: <5182@lynx.UUCP>
Date: 11 Jan 89 01:33:11 GMT
References: <597@mks.UUCP> <3845@pt.cs.cmu.edu> <18123@santra.UUCP> <5178@lynx.UUCP> <492@babbage.acc.virginia.edu>
Reply-To: m5@lynx.UUCP (Mike McNally)
Organization: Lynx Real-Time Systems Inc, Campbell CA
Lines: 29

In article <492@babbage.acc.virginia.edu> mac3n@babbage.acc.virginia.edu (Alex Colvin) writes:
>presumaby you expect C to detect arithmetic overflow as well.
>and subscript errors.
>and invalid pointers
>and ...

You presume wrong.

>C is not a high level language.

Bullshit.

>C is not a language for the average programmer.
>its wholesale adoption by the PC community is a disaster
>for both the language and that community.
>perhaps you should consider something in the Pascal line.

I don't program PC's unless it's under my own OS; even then I consider
them to be hideous piles of festering reeking mucous.  The issue has
nothing to do with that, however.  Whatever kind of language you think
C is, it has a semantic definition.  If a compiler does not implement
the required semantics, it's busted.  If you don't mind using it, go
for it; I don't give a cold bucket of piss.

-- 
Mike McNally                                    Lynx Real-Time Systems
uucp: {voder,athsys}!lynx!m5                    phone: 408 370 2233

            Where equal mind and contest equal, go.