Re: Get_Immediate warning, (was: How to get a character?)

[JS <john.doe@ddre.dk>]

Robert Dewar wrote:
> 
> In article <371304D4.81D40292@ddre.dk>,
>   JS <john.doe@ddre.dk> wrote:
> > Since Get_Immediate is much less used,
> > You can never be sure if it really works as it is
> > supposed to until you have verified it yourself for the
> > compiler at hand.
> >
> > One recent example is Object-Ada version 7.1.1 where it
> > did not !
> 
> That's not the right point of view. The issue here is
> one of implementation dependence, 

.. <snip diverse interesting stuff>

Sorry for failing to say, that the error in OA 7.1.1 was with the
non-blocking get_immediate(ch,avail), and that the error has been
corrected in OA 7.1.2.

Get_immediate(ch,avail) is supposed to return immediately, whether a key
is pressed (Avail=FALSE) or not (Avail=TRUE).

However, using OA 7.1.1, this only happened some of the time, not every
time.
Some times, get_immediate(ch,avail) instead would wait for a keypress, 
just like the "normal" get_immediate(ch).  

I would not call this an implementation dependance, but a compiler bug.

And I maintain, that the prudent user must be more careful of running
into 
hitherto unknown compiler bugs when he is using the outskirts of the
language, than when staying with mainstream features. 

Greetings,