home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / lang / function / 934 < prev    next >
Encoding:
Internet Message Format  |  1992-07-21  |  1.2 KB
  1. Path: sparky!uunet!mcsun!uknet!mucs!m1!sewardj
  2. From: sewardj@cs.man.ac.uk (Julian Seward (DRL PhD))
  3. Newsgroups: comp.lang.functional
  4. Subject: Re: Typing and Expressiveness
  5. Message-ID: <SEWARDJ.92Jul21132952@r6.cs.man.ac.uk>
  6. Date: 21 Jul 92 12:29:52 GMT
  7. References: <1992Jul12.061122.8943@eng.umd.edu>
  8.     <NICKH.92Jul14151920@VOILA.VENARI.CS.CMU.EDU>
  9.     <1992Jul14.205627.25659@eng.umd.edu> <1992Jul15.002311.27895@udel.edu>
  10.     <knight.711224199@cunews> <farrell.711260486@coral.cs.jcu.edu.au>
  11.     <knight.711298049@cunews> <92199
  12. Sender: news@cs.man.ac.uk
  13. Organization: Department of Computer Science, University of Manchester
  14. Lines: 13
  15. In-reply-to: brendan@cs.uq.oz.au's message of 20 Jul 92 06:21:38 GMT
  16.  
  17.  
  18. | How's this for an explanation.
  19. | 
  20. | With a statically typed language you not only specify a calculation to
  21. | be performed, but also a consistency check on your program text which
  22. | highlights really stupid mistakes. That is, you are actually writing two
  23. | programs with the one piece of text.
  24.  
  25. Or how about: with a statically typed (functional) language,
  26. the typechecker automatically constructs a proof that the
  27. program will not fall over with a segmentation fault when run.
  28.  
  29. So much more convenient than C.
  30.