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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,319ef0454c7765d5
X-Google-Attributes: gid103376,public
From: ka@socrates.hr.att.com (Kenneth Almquist)
Subject: Re: Why no exception hierarchy ?
Date: 1995/04/07
Message-ID: <D6nC0r.JC4@nntpa.cb.att.com>#1/1
X-Deja-AN: 100939432
sender: news@nntpa.cb.att.com (Netnews Administration)
references: <3ksv4s$f9e@news.uni-c.dk> <3l1mgn$ppb@gnat.cs.nyu.edu>
 <Mats.Weber-3103951843080001@mlma11.matrix.ch> <3ls5v8$nma@gnat.cs.nyu.edu>
 <Mats.Weber-0604952027340001@mlma11.matrix.ch>
organization: AT&T
newsgroups: comp.lang.ada
Date: 1995-04-07T00:00:00+00:00
List-Id: <comp.lang.ada>

Mats.Weber@matrix.ch (Mats Weber) asks:
> not. But then, how is it [POSIX error identification] done, since there
> are no task identifications in Ada 83 ?

The interface to errno defined by POSIX.5 is procedural.  Get_Error_Code
returns the current value of errno, and Set_Error_Code sets errno.  This
allows a variety of implementations.  As far as I can tell, all require
some assistance from the run time system, but since other parts of POSIX.5
require assistance from the run time system, this is not a major issue.
				Kenneth Almquist