From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: (format "Hello %1$S%2$s" 'world "!") Date: Fri, 22 Dec 2017 21:50:06 +0000 Message-ID: References: <061782A1-0A51-49A1-9AA4-706AF8927D01@gmail.com> <94EF128F-6A3D-41DD-B92D-0C165A4A8EB9@gmail.com> <617557F2-0316-4504-BE80-E7F29E4EE347@gmail.com> <86E604C6-4A01-42D2-A3CD-D758FC5DD8B1@gmail.com> <6fc86e25-4515-0787-d984-9160bc9c15e7@gmail.com> <3ea9c72e-352e-67d6-1c85-64441d458b4a@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114fcfe055b8f50560f4cdf1" X-Trace: blaine.gmane.org 1513979344 18814 195.159.176.226 (22 Dec 2017 21:49:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 22 Dec 2017 21:49:04 +0000 (UTC) Cc: Emacs developers , Noam Postavsky To: =?UTF-8?Q?Cl=C3=A9ment_Pit=2DClaudel?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 22 22:49:00 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eSVBV-000478-8J for ged-emacs-devel@m.gmane.org; Fri, 22 Dec 2017 22:48:53 +0100 Original-Received: from localhost ([::1]:39239 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSVDT-0005dL-GE for ged-emacs-devel@m.gmane.org; Fri, 22 Dec 2017 16:50:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36046) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSVCs-0005dG-Np for emacs-devel@gnu.org; Fri, 22 Dec 2017 16:50:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSVCr-0004l5-Lh for emacs-devel@gnu.org; Fri, 22 Dec 2017 16:50:18 -0500 Original-Received: from mail-qk0-x22a.google.com ([2607:f8b0:400d:c09::22a]:34225) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eSVCr-0004ko-HB for emacs-devel@gnu.org; Fri, 22 Dec 2017 16:50:17 -0500 Original-Received: by mail-qk0-x22a.google.com with SMTP id g81so6561033qke.1 for ; Fri, 22 Dec 2017 13:50:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ph66ctv8AcsKuHZxkO6mYA0/KQzalvdDaiqC6p0tvyM=; b=LjO1QwT/4xIzLpkW6LxOmzv80/HUFIxtDKr1wTzXvtJoXOU++FwWikZcDfrLR27O/i OtOWTXSQMiVQeU8yN5/f3wgS5Qsl98xthv57BhLUsUk68c44yV8HkapYsDz0ezPauwEE iaZQhfWW6jOuGkLEPewDlmKnHBjEckjmyHizGdmd7+OTZCVlKFpcCvxsjaqgWly/UaTf mNitf+1qA1GXI4qzZYH/ijCOMxcvNJ7V/wmL4o/DmBEiSOiXwIjzoRf8iMZGZY/cWIyN bFEKxa5V3Oq/5mi7E4W3uSC980XesqE328bdx7BRfgy3rlT2mo7Gi/TKwjQkTxj+zWaQ ExPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ph66ctv8AcsKuHZxkO6mYA0/KQzalvdDaiqC6p0tvyM=; b=Zo7iGfmtDqlUWyKA+poBVyX1zHZQoB3Sh38OBQNZtigoGAzaWQ59ltNsAxsogQMp8/ As6hHc56mzw2Hpp8fPijiq1TsbZMJPpk+ceTPeYQtxGeUkawjkD/JRsdzovFj3B5cDHw vDUJja4NRgYi0/fuFoC8wA0fsbqxo30a4gpvDnR1N4teWaI7kuNUq2vEPjwO9MdmGXa0 SIrs0p9irxK19Sk3mjDIav+t0ncz2GXZ0yNLaYMTdLCmx6UgjlCyfoSWj/VPODh0ckVS +BiUiHUSlPSFbmKUPZGqXLGVt1dqIfqedKfQP/wLiRpgn8zKuTjL+2B8ecMgaMly1ntH yi2Q== X-Gm-Message-State: AKGB3mIsmOxtjvv/Qn0fHdRG2a8uU6UMuKHqdx/tAzu6zlNMPFysp9+K aSKB6xExOH57QsJ4vD5BXej0DG6qi5vnanDdLlc= X-Google-Smtp-Source: ACJfBos78pt8hxguuPEBjIaAtS/bdp3I0VlVqQZQBe9c3vdG8Mqql6mAeHwr3BcwDbt9AU/biJlK6W24F1BwjNoSk1Q= X-Received: by 10.55.162.23 with SMTP id l23mr12926053qke.29.1513979416785; Fri, 22 Dec 2017 13:50:16 -0800 (PST) In-Reply-To: <3ea9c72e-352e-67d6-1c85-64441d458b4a@gmail.com> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400d:c09::22a X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221359 Archived-At: --001a114fcfe055b8f50560f4cdf1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cl=C3=A9ment Pit-Claudel schrieb am So., 2. Juli 20= 17 um 19:26 Uhr: > On 2017-07-02 12:54, Noam Postavsky wrote: > > On Sun, Jul 2, 2017 at 12:32 PM, Cl=C3=A9ment Pit-Claudel > > wrote: > >>> Why would we need a new function since %n$ would be an error for the > old format anyway? > >> > >> This in itself is a good reason to have a new function. A new functio= n > lets you migrate existing code, including plugins, to the new syntax, and > load the polyfill in older Emacsen. A new syntax that causes errors in o= ld > Emacsen isn't usable by anyone outside of Emacs core, for fear of > compatibility problems. > > > > We can still give a new name I suppose. > > I think it would be nice, if we also write a polyfill. If we don't intend > to write one, then there's probably no point. > We can't write a polyfill, just like browser developers can't write polyfills (if they do so, it's just normal functionality). Third-party library authors can write polyfills, of course, if they want. --001a114fcfe055b8f50560f4cdf1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


Cl=C3= =A9ment Pit-Claudel <cpitclaude= l@gmail.com> schrieb am So., 2. Juli 2017 um 19:26=C2=A0Uhr:
On 2017-07-02 12:54, Noam Postavsky wrote:=
> On Sun, Jul 2, 2017 at 12:32 PM, Cl=C3=A9ment Pit-Claudel
> <cpitcla= udel@gmail.com> wrote:
>>> Why would we need a new function since %n$ would be an error f= or the old format anyway?
>>
>> This in itself is a good reason to have a new function.=C2=A0 A ne= w function lets you migrate existing code, including plugins, to the new sy= ntax, and load the polyfill in older Emacsen.=C2=A0 A new syntax that cause= s errors in old Emacsen isn't usable by anyone outside of Emacs core, f= or fear of compatibility problems.
>
> We can still give a new name I suppose.

I think it would be nice, if we also write a polyfill. If we don't inte= nd to write one, then there's probably no point.
<= br>
We can't write a polyfill, just like browser developers c= an't write polyfills (if they do so, it's just normal functionality= ).
Third-party library authors can write polyfills, of course, if= they want.
--001a114fcfe055b8f50560f4cdf1--