From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: Serious IMAP problems because Gnus doesn't behave RFC compliant
Date: Thu, 04 Oct 2007 00:33:38 +1000 [thread overview]
Message-ID: <87k5q4jmil.fsf@enki.rimspace.net> (raw)
In-Reply-To: <smubqbg2xer.fsf@linuxpal.mit.edu>
Greg Troxel <gdt@work.lexort.com> writes:
> Simon Josefsson <simon@josefsson.org> writes:
>> Elias Oltmanns <eo@nebensachen.de> writes:
>>
>>> it would appear that Gnus currently by design cannot possibly comply
>>> with RFC 3501. The problem is that according to RFC 3501 a UID may
>>> be any 32bit unsigned integer, whereas ELisp only supports 28bit
>>> signed integers---on my system anyway.
>>
>> Wasn't the bit size increased recently? But still, on 32-bit systems
>> it still isn't the full 32 bits. On 64-bit systems, though, I
>> believe elisp integers can hold close to 64-bits.
>
> The notion that correct behavior depends on the machine architecture
> is unsettling, particularly in a lisp-like language. As I'm sure you
> know, Scheme simply deals with numbers of arbitrary size.
>
> I find it surprising that emacs doesn't have a 'int64_t' type, even if
> it's only 62.
Yah, it is a bit annoying. The CVS repository is --> that way, please
fix it. I would be very happy with you. ;)
Regards,
Daniel
--
Daniel Pittman <daniel@cybersource.com.au> Phone: 03 9621 2377
Level 4, 10 Queen St, Melbourne Web: http://www.cyber.com.au
Cybersource: Australia's Leading Linux and Open Source Solutions Company
next prev parent reply other threads:[~2007-10-03 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 7:50 Elias Oltmanns
2007-10-03 10:48 ` Simon Josefsson
2007-10-03 12:30 ` Greg Troxel
2007-10-03 14:33 ` Daniel Pittman [this message]
2007-10-03 13:12 ` Reiner Steib
2007-10-03 14:20 ` Simon Josefsson
2007-10-09 19:07 ` Ken Raeburn
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=87k5q4jmil.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--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).