From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,14aa27db81ce3b40
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Thu, 07 May 2009 12:01:28 +0200
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: How to exit an Ada program with (unix shell) error code?
References: 
 <49ba30c9-a1e6-4346-8618-d256f87ac301@s31g2000vbp.googlegroups.com>
  <356247f9-4a83-44aa-a412-4500e6af19cf@f1g2000prb.googlegroups.com>
 <2yxMl.30237$941.3661@bgtnsc04-news.ops.worldnet.att.net>
In-Reply-To: <2yxMl.30237$941.3661@bgtnsc04-news.ops.worldnet.att.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Message-ID: <4a02b178$0$31872$9b4e6d93@newsspool3.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 07 May 2009 12:01:28 CEST
NNTP-Posting-Host: ce526455.newsspool3.arcor-online.net
X-Trace: 
 DXC=ieU0[e^L<2;i6K;>iZ]763McF=Q^Z^V384Fo<]lROoR1^YC2XCjHcb9VFX03I1?Jb0;9OJDO8_SK6NSZ1n^B98i:>a@85Q^7g91
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:5724
Date: 2009-05-07T12:01:28+02:00
List-Id: <comp.lang.ada>

anon schrieb:
> Using a "function" type of module install 
>         program is the only way a "Module" can be written and have an 
>         "exit status".

Uhm, no.

Actually, the clean up routines of modules (assuming
Linux kernel modules) have "void" return type.


>         Note: Ada as a computer language should be allowed to create 
>               these type of programs which means that Ada needs to 
>               support main subprogram that are functions.

What seems needed is a way to write programs such that
they follow the conventions of the respective execution
environment; communication; interrupts; special locations;
and maybe return values.

This will necessarily depend on the execution environment,
I should think, which may or may not require *some*
subprogram to be a function with parameters, say.