Hi, El Thu, 02 November 2000, Dave Thomas escribióº > time.c: > > /* value validation */ > if ( tm->tm_year < 69 > || tm->tm_mon < 0 || tm->tm_mon > 11 > || tm->tm_mday < 1 || tm->tm_mday > 31 > || tm->tm_hour < 0 || tm->tm_hour > 23 > || tm->tm_min < 0 || tm->tm_min > 59 > || tm->tm_sec < 0 || tm->tm_sec > 60) > rb_raise(rb_eArgError, "argument out of range"); So, months start to count in 0, but days in 1... I have always wondered why this aberrant asimmetry... Why is it? And more importantly, can we throw it away? What would we be breaking? Either everything starts from 0 or everything starts from 1, that's the least surprise principle in action, isn't it? Also, ISO 8601, allows hour '24' as a equivalent to '00' and I have read somewhere that the may be a second '61' some times, but I haven't found that in any official document, so there's nothing solid in that... > Sorry... Mmmm... Are you guilty for that? If not, I don't think you should feel sorry, just worried like the rest of us ;-) Thn, david PS- thn for the CORBA link, but the documentation is in japanese, no configuration scripts, so little use for me in this Solaris... it's a mess of an installation and I cannot do a thing to fix it... In my Linux box I'd be able to hand-configure the Makefile, but... thn anyway, d@ ---------------------------------------------------------------------- + Mensaje enviado gracias al correo gratuito de Desmasiado Corp. + + http://correo.demasiado.com + ----------------------------------------------------------------------