iso - Do NodaTime constructors accept 24 in the Hours parameter -

i hoping quick answer 1 question nodatime before downloading it. far, reading nodatime , api , seems thought out.

i hope might eliminate of chaos i've been encountering in application has database back-end, desktop client database provider, , web client must run on major browsers. support iso 8601 on datetime , time varies on various database, database provider, , web platforms. internet explorer, example, follows iso 8601 sql server not; web ui timepickers not because chrome not.

question: in nodatime, 24:00 valid time value? 24 valid argument hours parameter of time constructors?

background: iso 8601 allows 2 representations of midnight: 00:00 "midnight morning" , 24:00 "midnight tonight". when datetime object on time-line, date time element has 24:00 coincides next day @ 00:00. same time-line instant 2 different representations, both representations valid per iso.

a time-only value detached time-line. time of 00:00 occurs @ beginning of detached 24-hour day , time-only value of 24:00 24 hours after 00:00. time type should accept 24 in hour. when 24 hour maximum value seconds , milliseconds , ticks 0 (unless modulo arithmetic involved , time rolls over, 24:01 00:01 -- iso has nothing implementation detail, iirc).

we accept 24:00 when parsing localdatetime, not 24:01.

this issue 153, implemented in revision f7ac0365d8ca.

unfortunately after 1.0 release, you'll either need grab current code, or wait 1.1 released (hopefully soon).

we don't accept when parsing localtime. if want that, please log feature request - we'd @ 1.2 (which have lot of text features), although i'm not sure representation like. (localtime doesn't support idea of "end-of-day midnight".)