🚀 go-pugleaf

In article <1992Dec28.184038.20725@nntpd.lkg.dec.com> feldman@speedy.zko.dec.com (Gary Feldman) writes:
>
>More importantly, allowing the assembly language view to influence your
>coding is more likely to be a source of bug-ridden programs, and not
>a preventative.  

	Trying to write programs without understanding machine
principles?

>This is especially true these days when more and more
>programs are being written to run on multiple architectures.  In such cases,
>assumptions made at the assembly level on one machine can be horribly invalid
>on another.  All sorts of things -- pointer arithmetic, alignment assumptions,
>speed assumptions, big endian vs. little endian, regiter behavior, casting
>behavior -- can break.

	How could you possibly understand any of these issues *without*
knowing some basic machine principles?

>
>If your goal is bug-free programs, then except for some limited problem domains,
>it is far more important to really understand the abstract semantics of C 
>independently of any assembly language, as well as quality design and testing
>methodologies.  
>

	I cant agree, if only because understanding the abstract
principles is extremely hard for even the brightest of us.

	For example, what is a 'type'?
	What is an 'object'?
	What is an 'lvalue'?
	What is a 'subtype'?

-- 
;----------------------------------------------------------------------
        JOHN (MAX) SKALLER,         maxtal@extro.ucc.su.oz.au
	Maxtal Pty Ltd, 6 MacKay St ASHFIELD, NSW 2131, AUSTRALIA
;--------------- SCIENTIFIC AND ENGINEERING SOFTWARE ------------------