From: Robert Horn <rjhorn@alum.mit.edu>
To: emacs-orgmode@gnu.org
Subject: Re: dates before 1970
Date: Sat, 12 Mar 2011 17:38:34 -0500 [thread overview]
Message-ID: <4D7BF5EA.7000109@alum.mit.edu> (raw)
In-Reply-To: <52DFBD89-0FCB-4546-85F1-254370ADE4E0@gmail.com>
> So I am not sure what 64 bit systems do now or in the future, but
> it seems that we need to live with a restriction for now.
> Maybe this should be documented somewhere.
>
> - Carsten
Most 64-bit systems use a 64-bit int. All of the 64-bit Linux systems
that I've used use a signed 64-bit int. Some systems use a 64-bit
unsigned int. Some use a double. The only way to know for sure is to
look at their definition of time_t in time.h, as provided by the system.
http://en.wikipedia.org/wiki/Time_t is as good a starting point as any.
The precise words from the Open Group Base standard are:
time_t and clock_t shall be integer or real-floating types.
The usage of time_t in various functions is specified, but range and
type is not defined.
R Horn
next prev parent reply other threads:[~2011-03-12 22:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 21:00 dates before 1970 Eric S Fraga
2011-03-10 23:06 ` Nick Dokos
2011-03-11 8:31 ` Bastien
2011-03-11 8:52 ` Carsten Dominik
2011-03-13 7:39 ` Carsten Dominik
2011-03-13 20:08 ` Eric S Fraga
2011-03-14 7:40 ` Carsten Dominik
2011-03-14 9:58 ` Bastien
2011-03-11 8:47 ` Eric S Fraga
2011-03-11 11:36 ` Carsten Dominik
2011-03-11 12:00 ` Eric S Fraga
2011-03-11 15:28 ` Carsten Dominik
2011-03-11 17:56 ` Gregor Zattler
2011-03-12 22:38 ` Robert Horn [this message]
2011-03-11 16:30 ` Nick Dokos
2011-03-14 10:21 ` Carsten Dominik
2011-03-14 15:11 ` Nick Dokos
2011-03-14 17:02 ` Carsten Dominik
2011-03-14 17:13 ` Nick Dokos
2011-03-14 18:12 ` Achim Gratz
2011-03-15 7:24 ` Carsten Dominik
2011-03-11 16:16 ` Nick Dokos
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7BF5EA.7000109@alum.mit.edu \
--to=rjhorn@alum.mit.edu \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).