Re: Package Proposal - DateRange and Range

MFriedman@symcor.com wrote:

I'm inclined to think of Ranges as entities and as such their own "type". While DateRange provides functionality related to Dates, a DateRange is not a Date, it is a Range. Much the same, if you think of an IntegerRange, you can't really call that an integer, it's also a Range. With regards to Validate, while I see that Range has some validation features, it also has features totally unrelated to Validation (like merge()). As such, I don't see Range classes in the Validate category. The methods in Range apply to Ranges and as such I think this makes a case for having a Range category in

I don't think a category "Range" would make much sense, however, I think "Abstract Types" might make sense. The implementations like Date_Range should go under the type of their implementation (Number_Range under Numbers, Text_Range for alphabetizing under Text, etc.) I need more time to decide on the package before I can give a +1 or -1 Thanks, Greg