220 4441 article Path: news.gmane.org!not-for-mail From: Zhihao Yuan Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: std::putf now supports %N%, like Boost.Format Date: Thu, 16 May 2013 00:54:14 -0400 Lines: 28 Approved: news@gmane.org Message-ID: References: <66ac5a48-8d1a-41f3-92ac-085c3b7de87a@isocpp.org> <75cd8f0a-81be-40d5-84a5-69287b3b18e2@isocpp.org> <8a59c705-90ba-4e45-b9f8-4b0556e16032@isocpp.org> <2f4ea651-e0a4-4427-9e32-73a23c3a3e8a@isocpp.org> <83caa602-33d7-491a-9620-5ab7711fb054@isocpp.org> <58823f67-4fa4-4fda-9a3b-452c32bfee27@isocpp.org> <671ee342-ad52-4a4c-8dda-847a61babc7b@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1368680058 19234 80.91.229.3 (16 May 2013 04:54:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 16 May 2013 04:54:18 +0000 (UTC) To: "std-proposals@isocpp.org" Original-X-From: std-proposals+bncBCUILMGRQMARB56M2GGAKGQEJMEEDNQ@isocpp.org Thu May 16 06:54:18 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-wg0-f72.google.com ([74.125.82.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UcqCm-0002LM-R3 for gclcip-std-proposals@m.gmane.org; Thu, 16 May 2013 06:54:16 +0200 Original-Received: by mail-wg0-f72.google.com with SMTP id e11sf2248097wgh.11 for ; Wed, 15 May 2013 21:54:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:received-spf:mime-version :x-received:in-reply-to:references:date:message-id:subject:from:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:list-subscribe:list-unsubscribe:content-type; bh=sCHAQkxiOect7lSeBGO/gNnxvjrrd7Lo6j6zJX2pCqw=; b=wmxY8VPAUMzBVwBusO6UTyJv4lXAb68qhLv3hZfCYtj/PWAIv7vN0k9+NiQAM8PaD/ agiuzLPTPluzohzyL4W4cPqMWk1vReA8+Tle/1zloGYIZmqRse5Or7dskfi6yIoRin5W G09oVrNH+I9MZjQnEcVvHzEgTo9LI/zZPhSeN2xaWQHCyQphqnSoS5XhOdyoTgYWgSS9 bdViwrka2xAZjKPYJHH2UjwGODwCIw9OGsz1l4rEnSP1Xf0L1aX6wC7XnOD2oQhN1Rfp Kyi2G5OI/hX9ffqLCOxc4b2N7v6lto8326ciaR0h1PWO4UOG/8NnsWBQOo2RVelABaHQ X-Received: by 10.112.173.136 with SMTP id bk8mr12144918lbc.24.1368680056082; Wed, 15 May 2013 21:54:16 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.152.29.99 with SMTP id j3ls54232lah.104.gmail; Wed, 15 May 2013 21:54:15 -0700 (PDT) X-Received: by 10.112.138.100 with SMTP id qp4mr19399120lbb.84.1368680055064; Wed, 15 May 2013 21:54:15 -0700 (PDT) Original-Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [2a00:1450:4010:c03::22e]) by mx.google.com with ESMTPS id x8si1755717lad.93.2013.05.15.21.54.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 May 2013 21:54:15 -0700 (PDT) Received-SPF: pass (google.com: domain of lichray@gmail.com designates 2a00:1450:4010:c03::22e as permitted sender) client-ip=2a00:1450:4010:c03::22e; Original-Received: by mail-la0-f46.google.com with SMTP id fk20so2569166lab.33 for ; Wed, 15 May 2013 21:54:15 -0700 (PDT) X-Received: by 10.112.126.165 with SMTP id mz5mr2664435lbb.62.1368680054755; Wed, 15 May 2013 21:54:14 -0700 (PDT) Original-Received: by 10.112.59.233 with HTTP; Wed, 15 May 2013 21:54:14 -0700 (PDT) In-Reply-To: X-Original-Sender: lichray@gmail.com X-Original-Authentication-Results: mx.google.com; spf=pass (google.com: domain of lichray@gmail.com designates 2a00:1450:4010:c03::22e as permitted sender) smtp.mail=lichray@gmail.com; dkim=pass header.i=@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:4441 Archived-At: On Wed, May 15, 2013 at 11:08 PM, Nicol Bolas wrote: > That is, if you provided a > standard-conforming printf format to putf, it would work as expected. If you > don't, then you get undefined behavior from putf. Errr, not quite. `putf` has no undefined behavior. Everything not being well defined in `printf` results in a less feature complete (from the point of view of C-printf, but not iomanip) output, or a failbit on the stream. I consider any thing not well-defined in `putf` as a bug (it makes no sense to have UB in a string formatting facility, seriously). -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___________________________________________________ 4BSD -- http://4bsd.biz/ -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/?hl=en. .