🚀 go-pugleaf

bruce@cheetah.inmos.co.uk (Bruce Stenning) writes:

>In article <cg.0afn@ami-cg.UUCP> cg@ami-cg.UUCP (Chris Gray) writes:
>>In article <1992Jul22.000454.24871@ccu1.aukuni.ac.nz> stuartw@ccu1.aukuni.ac.nz
>>writes:
>>My relevant experience: I've written an ANSI C compiler at work. I use
>>ANSI C at work almost exclusively. I've written other compilers, including
>>the one I use here at home. I've probably written over half a million lines
>>of high-level-language code over the years, so I've learned a LITTLE about
>>how to do it in a maintainable way, usually without sacrificing efficiency.

well...I never said this...perhaps you got the wrong from line????

>One question:  Do you consider C a high-level language?  I'd call a low
>level language with the typing and control of a high-level language. 
>There are a lot of things you can do in C that would be far less
>efficient in any other language.  The beauty of C is that it allows the
>programmer to write code that checks itself rather than this being done
>by the compiler.  It is very good practise to write code that is
>thoroughly checked than hope the compiler will catch it for you. 
>Writing well-documented C code with meaningful variable names will mean
>that it will be maintainable and very efficient.

>Can you imagine writing something like UNIX in Pascal?  It would be an
>absolute nightmare.