>   $hour  =  0 .. 24  

Did you mean 0 .. 23?

 >   $wday  =  1 .. 7     # 1 == Sunday, 7 == Saturday
   
 > I'm still a little uneasy about C<$wday> starting with 1 == Sunday, just
 > because Monday seems like the first day of the week to me. But I'm not
 > the one writing the calendars, and it seems silly to only have one value
 > that's 0-indexed. Oh, well. :-)

I am strongly opposed to this.  $wday should remain 0 .. 6.

Reasons:

1. People don't use numeric days of the week the way they use numeric
   months.  (At least nobody I know does.)  We want the month to be
   1-based to conform to the way people use numeric months.  This
   doesn't apply to the day of the week.

2. It means "@dow = qw(S M T W T F S);" works as expected, without
   having to introduce a bogus 0th element..

3. Date systems that count days since some epoch (like the Julian
   date) calculate day of week with ($date % 7), which of course is in
   the range 0 .. 6.  And with most such systems, 0 is Sunday.

4. That's what localtime did, and everybody's used to it.

I can't think of one advantage to having $wday be 1 .. 7.  (Well,
Microsoft Excel uses 1 .. 7, but I'm not sure that's an advantage. :-)
As for being the only 0-based field, what about $hour, $min, and $sec?

-- 
Chris Madsen              http://www.trx.com      [EMAIL PROTECTED]
TRX Technology Services                                 (214) 346-4611

Reply via email to