Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 91693 invoked by uid 500); 15 Apr 2003 20:12:52 -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 91682 invoked from network); 15 Apr 2003 20:12:51 -0000 Message-ID: <3E9C67FF.5020904@attglobal.net> Date: Tue, 15 Apr 2003 16:13:51 -0400 From: Jeff Trawick Reply-To: trawick@attglobal.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "William A. Rowe, Jr." CC: dev@apr.apache.org Subject: Re: [PATCH] hex format string for apr_uint64_t References: <3E9C483F.2060804@attglobal.net> <3E9C483F.2060804@attglobal.net> <5.2.0.9.2.20030415144838.02ec3c90@pop3.rowe-clan.net> In-Reply-To: <5.2.0.9.2.20030415144838.02ec3c90@pop3.rowe-clan.net> 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 William A. Rowe, Jr. wrote: > At 01:05 PM 4/15/2003, Jeff Trawick wrote: > >>Jeff Trawick wrote: >> >>>An unfortunately ugly example: >>> apr_time_t now; >>> apr_snprintf(..., "microsecs in hex: %" APR_UINT64_T_HEX_FMT, >>> (apr_uint64_t)) >> >>err, that last line should be >> >> (apr_uint64_t)now) > > > Of course :-) > > ... we will have to see how many platforms contradict > themselves between d and x formats - but I hope we find this isn't > a common problem. Like any other new feature it will just have to get verified by the pioneers that have access to such a box, if indeed one actually exists (can anybody say "malformed chunk header"???) I'm adding a couple of testcases to test/testfmt.c and will commit the set of changes once I see it do the right thing on a few boxes of differing word size and general temperament. Thanks, Jeff