On 2017 Jan 29 21:06:04, you wrote to me:

 NB>>> 3) Section F, The month variable is set to 0-11, and not 1-12. There
 NB>>> is no month 0, and would never be used that way. January is month
 NB>>> #1, December is month #12.

 ml>> on this you have to remember that programmers start counting at
 ml>> zero... january is month 0 and december is month 11... from zero to
 ml>> 11 is 12... zero is really a number even though some folks don't know
 ml>> that it is ;)

 NB> Then why is the "dayOfMonth" variable 1-31?

because that's how the code library routines work...

 NB> You cannot have it both ways.

this is ancient stuff, nick... it has been this way since the '80s or before...
most coders just use the runtime libraries that come with their compilers and
they have to conform to how they work... especially when converting things into
human readable format...

 NB> Stephen's original draft had a zeroToSixty variable, that was used for
 NB> both minutes as well as seconds. Obviously not all of those numbers
 NB> would have been used in the minutes variable, but they were there for
 NB> the using, regardless.

i don't know of anything that uses 60 in the minutes field but i suppose it is
possible...

 NB> If the "month" variable is going to use 0-11, then "dayOfMonth" should
 NB> use 0-30 to keep form with everything else listed there.

nope... see above about the existing runtime libraries that have been around
since forever...

 NB> But since there is no 0th day of the month, or no 0th month of the
 NB> year.. I think it should go that way instead. The definitions are
 NB> currently contradicting each other, whereas Stephen's ABNF reference
 NB> did not.

exactly why i suggested to leave the ABNF stuff alone contrary to what others
have been telling you...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Never walk out of a public restroom smelling your fingers.
---