| | | | | Browse by category |
Article ID: 819
Last updated: 05 Feb, 2008
Problem
When trying to create an RWTime beyond the year 2036 (specifically beyond Feb. 5, 2037, for most platforms) I get an invalid RWTime.
Cause
RWTime keeps the time as the number of seconds since 00:00:00 Jan. 1, 1901 GMT in an unsigned long variable. Feb. 5, 2037 represents the limit of the unsigned long on platforms with four-byte longs (MAX_ULONG). RWTime also can only correctly represent RWDates up to the year 2037.
Action
Derive from RWTime and extend this class.
When trying to create an RWTime beyond the year 2036 (specifically beyond Feb. 5, 2037, for most platforms) I get an invalid RWTime.
Cause
RWTime keeps the time as the number of seconds since 00:00:00 Jan. 1, 1901 GMT in an unsigned long variable. Feb. 5, 2037 represents the limit of the unsigned long on platforms with four-byte longs (MAX_ULONG). RWTime also can only correctly represent RWDates up to the year 2037.
Action
Derive from RWTime and extend this class.
This article was:
Helpful |
Not helpful
Report an issue
Article ID: 819
Last updated: 05 Feb, 2008
Revision: 1
Views: 4010
Posted: 25 Jun, 1997 by
Dean J.
Updated: 05 Feb, 2008 by
Dean J.
Also listed in
Others in this category
Why won't the InfoBrowser contents update in response to selection changes in ClassView or FileView?
Powered by KBPublisher (Knowledge base software)