Re: Package Proposal - DateRange and Range

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 PEAR. I'm not even sure that Validate is a "type" - (...what's a `Validate'?) it's more of a utility library for validation. Comments? Matt Friedman. "Stefan Neufeind" <stefan@neufeind. To: pear-dev@lists.php.net net> cc: MFriedman@symcor.com, Pierre-Alain Joye net> <paj@pearfr.org> Subject: Re: [PEAR-DEV] Package Proposal - DateRange and Range 18/08/2003 05:38 PM On 18 Aug 2003 at 17:24, MFriedman@symcor.com wrote: > The source code of both classes can be reviewed at: > http://www.daart.ca/php/range.php > > It's only partly done in terms of comments etc, but it should give a > clear indication of the purpose of the classes. > > The Validate package stuff sounds interesting but I'm not familiar > with the package. I'll have a look. Had a look also at the categorie "Date and time". There you find the package date. But I haven't had a look at it's code - maybe your DateRange-functions fit in there? But what you did were mainly validations, right? Have a look at date, too. I guess one of these two places is where your proposal might / should go. Stefan -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php