From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.bugs Subject: bug#29165: 26.0.90; can't use some code byte-compiled under emacs 24 Date: Mon, 06 Nov 2017 17:20:22 +0000 Message-ID: References: <6eh8u7x5be.fsf@just-testing.permabit.com> <87375r7f0g.fsf@users.sourceforge.net> <9f1e7a1f-bfc0-43a4-9acb-cf69b85587be@default> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114c8da6024f71055d53ac13" X-Trace: blaine.gmane.org 1509988873 18796 195.159.176.226 (6 Nov 2017 17:21:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 6 Nov 2017 17:21:13 +0000 (UTC) Cc: Ken Raeburn , 29165@debbugs.gnu.org, Noam Postavsky To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Nov 06 18:21:09 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1eBl5A-0004hw-4L for geb-bug-gnu-emacs@m.gmane.org; Mon, 06 Nov 2017 18:21:08 +0100 Original-Received: from localhost ([::1]:49406 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eBl5H-0000Oi-HO for geb-bug-gnu-emacs@m.gmane.org; Mon, 06 Nov 2017 12:21:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eBl57-0000MQ-IG for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2017 12:21:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eBl54-0005n5-7P for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2017 12:21:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:45765) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eBl54-0005mo-2u for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2017 12:21:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eBl53-00046D-TI for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2017 12:21:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Philipp Stephani Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Nov 2017 17:21:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 29165 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 29165-submit@debbugs.gnu.org id=B29165.150998884015715 (code B ref 29165); Mon, 06 Nov 2017 17:21:01 +0000 Original-Received: (at 29165) by debbugs.gnu.org; 6 Nov 2017 17:20:40 +0000 Original-Received: from localhost ([127.0.0.1]:54446 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eBl4h-00045P-HY for submit@debbugs.gnu.org; Mon, 06 Nov 2017 12:20:39 -0500 Original-Received: from mail-qk0-f174.google.com ([209.85.220.174]:47789) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eBl4g-000455-NU for 29165@debbugs.gnu.org; Mon, 06 Nov 2017 12:20:38 -0500 Original-Received: by mail-qk0-f174.google.com with SMTP id m189so11868462qke.4 for <29165@debbugs.gnu.org>; Mon, 06 Nov 2017 09:20:38 -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=XPAnLK2C5CIvC1bO13+LXllSbEaqz0afi3AZPuwf+GE=; b=WhVchnj8Tod0CBb3cNeP2JCZMVAZuaL5DuZzrcBPFu4mJ4G1YdXxryO2OK9G+AzuvR +9kwzgx9LSI/elgx9C8J+papXGT7nsVp7lJdQ1JpMoXgVxSPGVqsMP63n7zeuUzpX1P0 lWkHVIJSwgq8Zhopq0aKlmWfN7QW6XssZxltzkjdkyYp2ICpE0USIei2NZ/36dKvFQ7+ +QOqgO+uyPO7Da7F/m2AyzLB1IEXtGCWxMNJfGl9cnDDXQbfW8rsAS5q3V0KLxLcaRzy +pNYG52DVA+kmAgqo9+vUpaoRziMq3bnNHidaJUlgTqOLcNIS1VQSzumvSCvdNPbKFyb qLSA== 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=XPAnLK2C5CIvC1bO13+LXllSbEaqz0afi3AZPuwf+GE=; b=PcrwpBMzNwq6mNoWhGfADcvFqTM325t85RwG1VZA16Dsg4h+Rmbhm3HggOOHeuxjPQ j0d4BdRngs8m4/c7FHl4gf/jD5AhJSYvcb/kR2PxIrna6zmGgWYjqrNp8Iu/Q3bx52UP TCx9op2whk4pQVpY9+oLguvWiY59FeYH2Y99XCdZGqwcSpCgwrtRkD/VCw4myzxMIk2C g84AqZOWnsqPbHcW3VAlnh1IHTXa4N+rd6HLbL4ThVlPMCeYIQ5YFsaENfypUV254Exq g/Ne2WTxoG8CyGov7UFrbEmYxqxY9E6Wc7UiPEQBvmoAY7ZeQqJzDlZVSv0RSZtujNKt jJ/w== X-Gm-Message-State: AJaThX6ugj40pPf3JUPqlT7hb+RpUxeL8vq6fDmd5lZ7A2aDtj4P/GuT X4iRz+kjR5G/oKuQw0OGrOjHyOvbmlse0KOmIO8= X-Google-Smtp-Source: ABhQp+S+jtinPSh/2myMm0+s3YFjkr9H0EunBU5L7TzRTkqr2zz5gaP7BBm2Ggjbwr3cPs7uQl7/60/tqIvI1WraHRg= X-Received: by 10.55.90.66 with SMTP id o63mr5432346qkb.74.1509988833053; Mon, 06 Nov 2017 09:20:33 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:139510 Archived-At: --001a114c8da6024f71055d53ac13 Content-Type: text/plain; charset="UTF-8" Drew Adams schrieb am Mo., 6. Nov. 2017 um 15:41 Uhr: > > >> We should perhaps put something about throwing error on '&option > &rest' > > >> into NEWS though. > > > > > > I don't understand. In Common Lisp it is perfectly correct > > > to use both &optional and &rest. > > > > What's rejected is (&optional &rest other-vars), whereas (&optional > > var1 &rest other-vars) is okay. Does CL accept the first form (and if > > yes, what does it mean)? I couldn't tell from the page you linked to. > > CL accepts a single variable after &rest. And there must be > a variable after &optional. (&optional foo &rest bar) is OK. > > (&optional &rest foo) is not OK. > (&optional foo &rest bar toto titi) is not OK. > That should match the current behavior in Emacs Lisp now. --001a114c8da6024f71055d53ac13 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


Drew A= dams <drew.adams@oracle.com= > schrieb am Mo., 6. Nov. 2017 um 15:41=C2=A0Uhr:
> >> We should perhaps put something about throw= ing error on '&option &rest'
> >> into NEWS though.
> >
> > I don't understand.=C2=A0 In Common Lisp it is perfectly corr= ect
> > to use both &optional and &rest.
>
> What's rejected is (&optional &rest other-vars), whereas (= &optional
> var1 &rest other-vars) is okay. Does CL accept the first form (and= if
> yes, what does it mean)? I couldn't tell from the page you linked = to.

CL accepts a single variable after &rest. And there must be
a variable after &optional.=C2=A0 (&optional foo &rest bar) is = OK.

(&optional &rest foo) is not OK.
(&optional foo &rest bar toto titi) is not OK.

That should match the current behavior in Emacs Lisp now.= =C2=A0
--001a114c8da6024f71055d53ac13--