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,35629eebe01bcdaf
X-Google-Attributes: gid103376,public
From: "Tarjei Tj�stheim Jensen" <tarjei.jensen@kvaerner.no>
Subject: Re: About to give up...
Date: 1998/08/07
Message-ID: <6qem93$gg3@news.kvaerner.com>#1/1
X-Deja-AN: 378803785
Content-Transfer-Encoding: 7bit
References: <6qbtl7$v6$1@nnrp1.dejanews.com> <6qc8rf$cbo$1@nnrp1.dejanews.com>
Content-Type: text/plain; charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Organization: Kv�rner Oil & Gas
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1998-08-07T00:00:00+00:00
List-Id: <comp.lang.ada>


Oliver.Kelloggwrote :
>I once did a Terminal_IO package  (with procedures like
>Put_At (Row,Col, Text)) where the underlying system calls
>were functions that always returned a success/error status.
>Since this is not usually interesting, I introduced a body-global
>status flag and a function in the Terminal_IO package spec,
>Get_Last_Status. That way I could turn the Terminal_IO
>user level functions into procedures, and one could call
>Get_Last_Status for finding out the status of the last call if
>need be.


I thought that this is the problems exception was intended to solve. If the low
level routine discovers an error, then throw an exception. What could be
easier?


Greetings,