Re: Community Input for the Maintenance and Revision of the Ada Programming Language

[Dennis Lee Bieber <wlfraed@ix.netcom.com>]

ONE: Your question has nothing to do with "Community Input ... Revision
..." You really should have started a new topic rather than making your
question a reply to an existing thread.

TWO: It would have helped if you provided a description of what you
expected vs what you got from the program -- instead making one recreate
your program to test (UGH -- GPS 2017 looks ugly compared to what I've used
for the last decade or so).

On Mon, 2 Oct 2017 03:06:43 -0700 (PDT), reinert <reinkor@gmail.com>
declaimed the following:

>Not a big issue, but why does not this function:
>
>    if t1 < Clock and Clock < t2 then ...
>
>Should it?
>

	That snippet seems to work fine.

>Example code below for testing.
>
>reinert
>
>with Text_IO;
>use  Text_IO;
>with Ada.Calendar;
>use Ada.Calendar;
>procedure test1i is
> t1,t2 : time;
>begin
> t1 := Clock + 10.0;
> t2 := Clock + 20.0;
>
>-- bla bla..
>
>--  if t1 < Clock and Clock < t2 then -- this function
>    if Clock in t1 .. t2 then         -- this dows *not* function

	Well -- GNAT 2017 reports "scalar type required for range", which seems
rather self-explanatory... t1, t2, and by association, the value returned
from Clock, are not "scalar" values.

	"Time" type is defined as "private" in the standard, so could be made
up of anything internally. The comparison operator "<" (and others) are
defined in the calendar package, so are available for use in the first form
of the "if" statement.

-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/