From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: "two time periods with only an endpoint in common do not overlap" ??? |
Date: | 2021-10-16 04:52:48 |
Message-ID: | f4d6745d-d16a-448b-5966-7e9f6e2e6682@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/15/21 11:35 PM, David G. Johnston wrote:
> On Friday, October 15, 2021, Ron <ronljohnsonjr(at)gmail(dot)com
> <mailto:ronljohnsonjr(at)gmail(dot)com>> wrote:
>
>
> The numeric ranges 0-10 and 10-19 overlap, just as the time ranges
> 00:01:00-00:00:02:00 overlaps 00:02:00-00:03:00.
>
> *It's the programmer's responsibility* to say what s/he really means,
> not for "the system" to make that choice.
>
>
> The system has canonical representation for discrete element range. The
> upper bound is exclusive, the lower bound is inclusive. All the docs are
> doing is stating the obvious consequence of that rule.
>
> The “numeric range 0-10” is under specified and thus, as written, one must
> abide by the rule, implying [). The programmer is free to fully specify
> their range to have the upper bound inclusive, but canonicalization would
> then just change it to be “0-11” with the [) implied.
Prima facie, if you were told "numbers in the range 0-10", would you really
think, "ah, they *really* mean 0 through 9"?
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2021-10-16 04:54:27 | Re: "two time periods with only an endpoint in common do not overlap" ??? |
Previous Message | David G. Johnston | 2021-10-16 04:35:04 | Re: "two time periods with only an endpoint in common do not overlap" ??? |