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: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: About to give up... Date: 1998/08/07 Message-ID: #1/1 X-Deja-AN: 379050998 References: <6qbt86$dh$1@nnrp1.dejanews.com> <6qcblu$f60$1@nnrp1.dejanews.com> <6qeb1u$728$1@nnrp1.dejanews.com> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 902546010 6112 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-08-07T00:00:00+00:00 List-Id: Dan said <<> As for the useless values, just put them into "Trash" variables. No big deal. True but tedious... >> Tedious for who? the reader, or the writer. Remember that we don't care two hoots about the writer in the Ada design if the writer's interest conflict with those of the reader. (or maintainer!) In fact the ease of accidentally ignoring returned values is one of the great weaknesses in C. C almost invites programs to avoid taking the effort to deal with error indications. If you *do* want to completely ignore returned result, I find a useful notation to be Discard (func (params)); where Discard is an inlined null procedure that ignores its parameter. But very often you will do better to do something like Check_Error (func (params)); where Check_Error checks that the returned result is OK, and raises an exception if not.