confused by ranges

[Dan Langille]

On 19 Sep 2004 at 10:24, Jacques A. Vidrine wrote:

> > This is an interesting example:
> > 
> >         <range><lt>1.1.2_1</lt></range>
> >         <range><ge>2.0</ge></range>
> > 
> > Two range statements in the same package... instead of one range with 
> > two operators.  Why?
> 
> Because they are two non-contiguous ranges and cannot be expressed by a
> single interval.  The two are:
> 
>             x < 1.1.2_1
>      2.0 >= x
> 
> or equivalently [0, 1.1.2_1) and [2.0, infinity).
> 
> 
> Hmm, re-reading what you wrote, it seems you want to think of it
> algorithmically.  In that case, you could interpret each <range> element
> as containing expressions that should be ANDed (although the number and
> form of the expressions are constrained by the DTD), while multiple
> <range> elements in one <package> should be ORed.

I found an error in my tables.

I was relating a range to a name.  That is incorrect.

A package may have many names.  The ranges in a package relate to all 
the names.

I've just changed my scipts and modified my DDL.

-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/