From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 10 Aug 93 13:19:44 GMT
From: cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!do
g.ee.lbl.gov!hellgate.utah.edu!peruvian.cs.utah.edu!matwood@ucbvax.Berkeley.EDU
  (Mark Atwood)
Subject: Re: SunAda Return Codes
Message-ID: <1993Aug10.071944.10852@hellgate.utah.edu>
List-Id: <comp.lang.ada>

In article <1993Aug9.131800.1757@news.eng.convex.com> pelakh@convex.com (Boris 
Pelakh) writes:
>In article <245b35$3r7@frigate.doc.ic.ac.uk> ajy@doc.ic.ac.uk (Andrew Young) w
rites:
>>How does a SunAda program report a return code to Unix?
>
>All you have to do is make your main a function returning integer instead of 
>a procedure, and then RETURN the proper code.

Please note, return values are implementation dependent, and are not defined
anywhere in the LRM.  Making the top-level subprogram a funtion returning an
integer is one solution the compiler writer may choose.  Or it may be included
in a OS isterface package.  I think the POSIX binding do this.

WRT the form of the top-level subprogram, the compiler must at least be able
to handle a procedure with no parameters.  Anything else is at the compiler
writer's discresion.

-- 
Mark Atwood                  | My school and employer have too many problems
matwood@peruvian.cs.utah.edu | without being blamed for mine.