From: Sebastian Spaeth <Sebastian@sspaeth.de>
To: Austin Clements <amdragon@mit.edu>,
Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
Cc: Patrick Totzke <patricktotzke@googlemail.com>, notmuch@notmuchmail.org
Subject: Re: [python] segfaults at Message.get_date
Date: Mon, 20 Jun 2011 09:29:22 +0200 [thread overview]
Message-ID: <878vsxvu3x.fsf@SSpaeth.de> (raw)
In-Reply-To: <BANLkTik8ged+SoUQf5=x0m-CDC6rAKUoWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Sun, 19 Jun 2011 19:51:11 -0400, Austin Clements <amdragon@mit.edu> wrote:
> A double will precisely represent integers up to 2^53, so this
> conversion shouldn't be a problem until the year 285422109 or so.
But given that it works, is it actually necessary, that xapian
apparently pulls an int from the database, returns a std::string to
libnotmuch, which calls a helper function to unserialize it to a double
and casts it to time_t before handing it to the user how probably uses
it as a long?
Can't we easily put in longs and get longs back?
Sebastian
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-06-20 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 21:54 [python] segfaults at Message.get_date Patrick Totzke
2011-06-17 6:34 ` Sebastian Spaeth
2011-06-17 16:10 ` Patrick Totzke
2011-06-18 10:30 ` Sebastian Spaeth
2011-06-19 9:45 ` Dmitry Kurochkin
2011-06-19 14:53 ` Sebastian Spaeth
2011-06-19 23:51 ` Austin Clements
2011-06-20 7:29 ` Sebastian Spaeth [this message]
2011-06-20 16:53 ` Austin Clements
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vsxvu3x.fsf@SSpaeth.de \
--to=sebastian@sspaeth.de \
--cc=amdragon@mit.edu \
--cc=dmitry.kurochkin@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@googlemail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).