Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!cmh117
From: CMH117@psuvm.psu.edu (Charles Hannum)
Newsgroups: comp.lang.c
Subject: Re: Malloc in Turbo C
Message-ID: <90060.160737CMH117@psuvm.psu.edu>
Date: 1 Mar 90 21:07:37 GMT
References: <26316@qfagus.OZ> <90058.153755CMH117@psuvm.psu.edu>
 <52749@bbn.COM>
Organization: Penn State University
Lines: 15


In article <52749@bbn.COM>, pdsmith@bbn.com (Peter D. Smith) says:
>
>Most implementations of C are screwed up: they give you a dangerous tool
>but don't give you a handle on double-checking the results.

Too much error-checking slows things down.  The assumption in C is that the
programmer *knows* what {s}he is doing.  With power come responsibility ...


Virtually,
- Charles Martin Hannum II       "Klein bottle for sale ... inquire within."
    (That's Charles to you!)     "To life immortal!"
  cmh117@psuvm.{bitnet,psu.edu}  "No noozzzz izzz netzzzsnoozzzzz..."
  c9h@psuecl.{bitnet,psu.edu}    "Mem'ry, all alone in the moonlight ..."