Re: Year 2038 problem with calendar (Bad holiday list items)

[Sascha Wilde <wilde@sha-bang.de>]

Glenn Morris <rgm@gnu.org> wrote:
> OK, now I can reproduce it on a 32-bit system. As has been said, it's
> because things like:
>
> (encode-time 1 0 0 1 1 2039)
>
> fail on such systems ("specified time is not representable").

So it's the classical y2038 problem.  :-)
(Which seems to be implicitly solved on 64bit systems, which is a good
thing to know...)

>> (setq calendar-dst-check-each-year-flag nil)
>
> This does avoid the problem for me.

Yes, works for me to.  However, the list is still much shorter than
that posted by Ed, I wonder why...

> I will see if this can be handled more gracefully, but I see no need
> for this to be changed before the release of Emacs 22. Assuming, as
> Nick says, that this happens in the next 30 years...

I agree, this is a minor issue.

cheers
sascha
-- 
Sascha Wilde
"Structure is _nothing_ if it is all you got.  Skeletons _spook_ people if
 thwy try to walk around on their own.  I really wonder why XML does
 not."            -- Erik Naggum <erik@naggum.net> in comp.lang.lisp