Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 87414 invoked by uid 500); 8 May 2001 16:23:31 -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 86560 invoked from network); 8 May 2001 16:23:22 -0000 Date: Tue, 8 May 2001 18:22:15 +0200 From: Luke Kenneth Casson Leighton To: Justin Erenkrantz Cc: Jeff Trawick , dev@apr.apache.org Subject: Re: [REPOST] printf and FMT values. Message-ID: <20010508182215.J10894@angua.rince.de> Mail-Followup-To: Justin Erenkrantz , Jeff Trawick , dev@apr.apache.org References: <20010430224440.F6283@ebuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010430224440.F6283@ebuilt.com>; from jerenkrantz@ebuilt.com on Mon, Apr 30, 2001 at 10:44:41PM -0700 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > > There is no need for apr_*printf formats to be compatible with OS printf > > > calls. We have re-implemented apr_*printf because we needed better > > > portability. In reality, that means that we could easily just define a > > > single set of format strings. > Well, the only glaring omission to apr_*printf() is support for "%lld" - the other one that you may wish to consider adding, at some point, is Unicode printfs. Win32 has %S for 'hey, am i in UNICODE mode? okay! let's convert this string to char*, then!' and vice-versa when you compile _not_ in Unicode-mode... otherwise, Win32 treats a %s as default-whatever-you-have-compiled-as [%s is Unicode when compiled as Unicode, char* when compiled as char*] luke