Re: Student views on Ada

[gasser@masg1.epfl.ch (Laurent Gasser)]

In the same vein, you may enjoy reading "Writing Solid Code" at
Microsoft Press.  Yes it is specific to C.  Yes it is edited by
Microsoft and written by one of its member.  But the spirit is quite
sound:

  Every time you find a bug, think about ways you had to catch it in 
  a systematic / automatic way.
  
Reading it is quite instructive.  But I still wonder why C is so
widely used...

In article <35kapa$1fqc@watnews1.watson.ibm.com>, ncohen@watson.ibm.com (Norman H. Cohen) writes:
|> 
|> Being aware that something is wrong when it is called to one's attention
|> is one thing; noticing an error--perhaps a clerical error, perhaps an
|> invalid but seductive line of subtle reasoning--when it's buried in a
|> large and complex program is something else.
|> 
|> Some C programmers, lacking a language that facilitates strong
|> consistency checks, may argue that such checks are for sissies--that Real
|> Programmers do not need them.  However, a compiler that performs strong
|> consistency checks is, like a spelling checker, an important tool for
|> protecting us from our imperfections.  Its use should be a part of the
|> state of the practice for responsible programmers, just as the use of a
|> safety belt is part of the state of the practice for window washers.  To
|> call it a bad habit is to deny that humans make errors.
|> 
|> --
|> Norman H. Cohen    ncohen@watson.ibm.com

-- 
Laurent Gasser (gasser@dma.epfl.ch)
Computers do not solve problems, they execute solutions.

I know very few ideas worth dying for, none is worth killing.