Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!homxb!genesis!hotlg!anumb!eao
From: eao@anumb.UUCP (e.a.olson)
Newsgroups: comp.lang.c
Subject: Re: Check for function results
Message-ID: <140@anumb.UUCP>
Date: Wed, 2-Dec-87 20:42:47 EST
Article-I.D.: anumb.140
Posted: Wed Dec  2 20:42:47 1987
Date-Received: Tue, 8-Dec-87 03:00:56 EST
References: <10530@brl-adm.ARPA>
Reply-To: eao@anumb.UUCP (e.a.olson)
Organization: AT&T Bell Labs, Andover MA
Lines: 10

In article <10530@brl-adm.ARPA> I1090801%DBSTU1.BITNET@CUNYVM.CUNY.EDU writes:
>I am a student of computer science and I have to write a C-compiler.
>The problem I came across is: does a C-compiler have to generate code
>to check if a function really delivers a result in all cases?
>Example: In the following (nonsense) function

    I seem to remember bing told in school, that in the absence of
    an explicit return, the return value would be the last expression
    evaluated in the function.  But I've never heard anything otherwise
    on the subject and it seems awfully implementation-dependent.