Re: prefixes and namespaces?
Matt Lewis wrote:
>
> Jeremy Cowgar wrote:
> >
> > Salix wrote:
> > >
> > > I vote for prefixes. I think the datetime_compare() example
> > > is great beacuse it shows how confusing it could be for a newbie.
> >
> > That's one big stumbling block to me about totally no prefix. I'd like to
> > hear
> > an solution that addresses compare() directly.
>
> Since the format of a datetime is:
> {year, month, date, hour, minute, second}
> ...it already works with the built-in compare, so datetime_compare() is
> redundant. If it didn't, an alternative solution would be to either
> make it so, or to call it something other than compare. Better to change
> one exception than an encumber an entire library.
It is because the current implementation use that data structure. (I simplified
it from the {{d,m,y},{h,n,s}} used by original datetime.e). But can we be sure
that it is fixed like that?
One pitfall for users: they won't be able to use built-in date() as argument to
compare().
|
Not Categorized, Please Help
|
|