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: Oliver.Kellogg@vs.dasa.de Subject: Re: About to give up... Date: 1998/08/06 Message-ID: <6qc8rf$cbo$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 378491735 References: <6qbtl7$v6$1@nnrp1.dejanews.com> Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Thu Aug 06 12:50:55 1998 GMT Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/2.0 (compatible; MSIE 3.02; Windows NT) Date: 1998-08-06T00:00:00+00:00 List-Id: In article <6qbtl7$v6$1@nnrp1.dejanews.com>, i96danma@my-dejanews.com wrote: > The first steps were no problem and I quickly got used to the API. The worst > problems though were [...], and the fact that you always have to take care of > the return values, even if you don't care. And it seems as Win32 returns a lot > of values that are, most of the time, unimportant. 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. -- $0.02, Oliver -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum