Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!jarthur!uunet!mcsun!inria!ilog!barbes!davis From: davis@barbes.ilog.fr (Harley Davis) Newsgroups: comp.object Subject: Re: Void references Message-ID: Date: 19 Nov 90 18:02:43 GMT References: <1990Nov7.220902.13393@Neon.Stanford.EDU> <454@eiffel.UUCP> Sender: davis@ilog.UUCP Organization: ILOG S.A., Gentilly, France Lines: 28 In-reply-to: bertrand@eiffel.UUCP's message of 14 Nov 90 18:17:19 GMT In article <454@eiffel.UUCP> bertrand@eiffel.UUCP (Bertrand Meyer) writes: 2. On the topic of errors: It is nice to see that apparently everyone agrees that there may remain errors at execution-time. The next question is: which ones? I have described a framework (Eiffel's) in which, assuming a perfect compiler, only three kinds of errors may remain: A. Attempt to call a feature on a void reference. B. Assertion violation. C. Hardware or operating system fault (e.g. arithmetic overflow). "Assertion violation" is a little vague as a type of error. What doesn't it cover? In particular, why can't it include type assertions (or other static errors normally caught by the perfect compiler) and void references? -- Harley Davis -- ------------------------------------------------------------------------------ Harley Davis internet: davis@ilog.fr ILOG S.A. uucp: ..!mcvax!inria!ilog!davis 2 Avenue Gallie'ni, BP 85 tel: (33 1) 46 63 66 66 94253 Gentilly Cedex France