Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: Orca/C bug (void functions)
Message-ID: <15770@smoke.brl.mil>
Date: 8 Apr 91 21:58:46 GMT
References: <1991Apr6.083344.26760@rbdc>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 24

In article <1991Apr6.083344.26760@rbdc> barry@rbdc.UUCP (Barry Newberry) writes:
-It appears that an old bug (feature?) has been left in Orca/C. Of course,
-I never wrote Mike (W.) about it, because I thought someone else would
-(my mistake). The compiler won't allow called functions to be type void.
-The compiler blames the next line of code for the problem.

Oh, good grief!  ORCA/C certainly does allow functions to have void
return type.

-void main (void)
-{
- thing ();
-}
-void thing (void)
-{
-}
-Compiling thing
-   7 {
-     ^ duplicate symbol

The compiler is perfectly justified in complaining about your attempt
to define thing() as returning void when previously you gave it an
implicit declaration (by invoking it in the absence of a prior
declaration) as returning int.