From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: cc-mode: Make all parameters introduced in Emacs 26 optional Date: Mon, 12 Mar 2018 21:00:33 -0400 Message-ID: References: <1516608561.1943450.1243462056.1A47A60F@webmail.messagingengine.com> <20180122203254.GA4888@ACM> <1520885798.1440538.1300560400.68951242@webmail.messagingengine.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1520902869 11656 195.159.176.226 (13 Mar 2018 01:01:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 13 Mar 2018 01:01:09 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 13 02:01:05 2018 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 1evYJN-0002m0-4K for ged-emacs-devel@m.gmane.org; Tue, 13 Mar 2018 02:01:05 +0100 Original-Received: from localhost ([::1]:36410 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evYLJ-0001Mk-Aa for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 21:03:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36223) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evYKe-0001Mb-TT for emacs-devel@gnu.org; Mon, 12 Mar 2018 21:02:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evYKb-0004vQ-1k for emacs-devel@gnu.org; Mon, 12 Mar 2018 21:02:24 -0400 Original-Received: from [195.159.176.226] (port=54918 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1evYKa-0004uZ-GL for emacs-devel@gnu.org; Mon, 12 Mar 2018 21:02:20 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1evYIQ-0001lK-K1 for emacs-devel@gnu.org; Tue, 13 Mar 2018 02:00:06 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 15 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:MiKi6+xH38MGoQXpXNlsFKYU31g= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:223675 Archived-At: >> (condition-case nil >> (call1 ...) >> (wrong-number-of-arguments >> (call2 ...))) > > Out of (mostly theoretical) curiosity: is there a way to restrict that > condition-case to that specific function call? (rather than catching all > incorrect calls in that call tree) No. Actually just defining the notion of "that specific function call" is already pretty tricky if you consider the case where `call1` is advised, for example. Stefan