Date: Sat, 27 Oct 2001 21:03:57 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Mike Smith <msmith@FreeBSD.ORG> Cc: arch@FreeBSD.ORG Subject: Re: 64 bit times revisited.. Message-ID: <200110280403.f9S43vm88827@apollo.backplane.com> References: <200110280349.f9S3n6v22087@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:
:> So far it's been amazingly painless. I really don't think this is going
:> to be as big a deal as some people think (or even as big a deal as I
:> thought it would be, I'm already half way there!). The next step for
:> me is to write the syscall roll functions and test a 64 bit time_t
:> kernel with a 32 bit time_t userland.
:
:Please write a library routine that detects and compensates for:
:
:
: int t;
:
: time(&t);
:
:Until you can do this, sorry, no.
Sorry, your statement makes no sense. Besides, if the programmer
includes time.h the above will generate compiler warnings, so
that's actually the easiest case to catch.
I'll tell you what, why don't YOU write a library routine that
detects this:
/* no includes */
int x;
lseek(fd, x, 0);
Oops! That doesn't work either! Are you going to change our off_t
from 64 back to 32 bits? No? Well, then I'm afraid you are going
to have to just live with it.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110280403.f9S43vm88827>