From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id CAB80385482C for ; Thu, 29 Oct 2020 15:49:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org CAB80385482C Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-99-mtHTLY7LN2KEMhUAgqds0w-1; Thu, 29 Oct 2020 11:49:03 -0400 X-MC-Unique: mtHTLY7LN2KEMhUAgqds0w-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id DA1FB809DFA; Thu, 29 Oct 2020 15:48:59 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-113-60.ams2.redhat.com [10.36.113.60]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C4E4D805DD; Thu, 29 Oct 2020 15:48:57 +0000 (UTC) From: Florian Weimer To: Adhemerval Zanella Cc: Adhemerval Zanella via Libc-help , ell1e Subject: Re: Is there a way to use vsnprintf_l? Would it possibly be considered for an addition one day, if missing? References: <87sga95u39.fsf@oldenburg2.str.redhat.com> <97ee03c7-29a7-e0a4-2aa2-462efbc494f0@linaro.org> Date: Thu, 29 Oct 2020 16:48:56 +0100 In-Reply-To: <97ee03c7-29a7-e0a4-2aa2-462efbc494f0@linaro.org> (Adhemerval Zanella's message of "Tue, 20 Oct 2020 10:30:43 -0300") Message-ID: <87zh45qbh3.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2020 15:49:08 -0000 * Adhemerval Zanella: >> I would prefer to wait for standardization: it is not quite clear what >> should happen if you use fwprintf_l on a wide stream that already uses a >> different charset. > > Is this being discussed somewhere? We already have at least one > implementation (not sure if MacOSX one is not the FreeBSD imported one > and if Windows one does follow the expected interface). Should we > block a possible implementation without proper standardization? What > about a non wide set of implementations, would be feasible? There is no strictly non-wide set of functions, due to %ls. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill