Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 91431 invoked by uid 500); 10 Jun 2002 22:54:47 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 91420 invoked from network); 10 Jun 2002 22:54:47 -0000 Message-ID: <3D052E3E.10006@cnet.com> Date: Mon, 10 Jun 2002 15:54:54 -0700 From: Brian Pane User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@apr.apache.org Subject: Re: apr_time_t --> apr_time_usec_t References: <00ad01c210cf$c9e86300$2200000a@KOJ> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ryan Bloom wrote: >This is going to break EVERY apr app out there. I have no problem with >the change, but everything is going to be broken. Is there any way to >do this by creating an apr_time32_t, or something that will keep the >default at 64-bit, and allow people to use 32 if they specify it? > How about leaving apr_time_t unchanged and adding an apr_timeval: typedef struct { unsigned tv_sec; unsigned tv_usec; } apr_timeval; plus apr_status_t apr_timeval_now(apr_timeval* time) to complement (not replace) the existing apr_time_now() and apr_timeval versions of other time functions. --Brian