From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Debugger entered--Lisp error: (overflow-error "13419098521433281274")
Date: Tue, 15 Mar 2011 17:50:04 +0100 [thread overview]
Message-ID: <m3zkowe3b7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <8739my3kmb.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> LMI> I think the best way to handle this is to make the MODSEQ into a string
> LMI> if it's more than mumble number of characters long.
>
> ...so basically replace (\d+) with "\1" if that's bigger than MAXINT?
I've now had a peek at the code, and we basically don't use MODSEQ from
FETCH at all. We use HIGHESTMODSEQ from SELECT, though, which has the
same problems.
So this is what I think should be done:
1) The parser should just remove "\\bMODSEQ ([0-9])" totally before
parsing FETCH
2) HIGHESTMODSEQ should be read as a string
3) The thing that compares old to new HIGHESTMODSEQ should take both
numbers and strings, but compare things as strings
I'll make those changes now.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-03-15 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 15:28 Tassilo Horn
2011-03-02 17:52 ` Tassilo Horn
2011-03-02 19:00 ` Andreas Schwab
2011-03-02 19:24 ` Tassilo Horn
2011-03-02 20:17 ` Ted Zlatanov
2011-03-02 20:36 ` Tassilo Horn
2011-03-02 20:52 ` Andreas Schwab
2011-03-02 21:02 ` Tassilo Horn
2011-03-02 20:56 ` Ted Zlatanov
2011-03-03 8:11 ` Tassilo Horn
2011-03-04 14:59 ` Ted Zlatanov
2011-03-05 10:52 ` Lars Magne Ingebrigtsen
2011-03-05 10:55 ` Lars Magne Ingebrigtsen
2011-03-07 17:29 ` Ted Zlatanov
2011-03-15 16:50 ` Lars Magne Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zkowe3b7.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).