Hi Ian, everyone,
Finally a moment to read the other comments here.
Am I correct in understanding that the cookie that should be accepted has
a latter time than 2038, meaning it is being rejected perhaps creating
part of the issue? I did note that the audio challenge is not working
and that even when properly solved the error still happens.
I am reconnecting with Amazon this evening, so wish confirmation that I
can share this discussion, and that my understanding is correct?
Thanks,
Karen
On Wed, 28 Aug 2019, Ian Collier wrote:
The year-2038 bug in Lynx appears to be in src/parsdate.y where it says:
/* See the LeapYears table in Convert. */
#define EPOCH 1970
#define END_OF_TIME 2038
So interestingly it will accept 31-dec-2038 even though that's after
32-bit day, but it does not acknowledge any year >2038.
This source file also contains a list of all leap years between the Epoch
and the 'End of time':
static const int LeapYears[] =
{
1972, 1976, 1980, 1984, 1988, 1992, 1996,
2000, 2004, 2008, 2012, 2016, 2020, 2024, 2028, 2032, 2036
};
I haven't really tried to parse the code in this function, but it seems
to me that most of the arithmetic could be done by mktime(3) these days.
imc
_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev
_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev
