From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Sun, 23 Feb 2020 20:34:48 +0100 Message-ID: <87v9nx3xnr.fsf@telefonica.net> References: <86wo8flqct.fsf@stephe-leake.org> <86sgj3ljf0.fsf@stephe-leake.org> <5fecc0e1-1ee2-5a89-9297-b0b9aa4a8e9c@cs.ucla.edu> <831rqli2gh.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="70047"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.60 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:c70GhzLIZsDXTwFzw781ERcdmAU= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 23 20:35:28 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j5x2G-000I9U-Be for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Feb 2020 20:35:28 +0100 Original-Received: from localhost ([::1]:56156 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5x2F-0007TD-DL for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Feb 2020 14:35:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47544) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5x1l-00073S-Fc for emacs-devel@gnu.org; Sun, 23 Feb 2020 14:34:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j5x1k-0005ie-Ki for emacs-devel@gnu.org; Sun, 23 Feb 2020 14:34:57 -0500 Original-Received: from ciao.gmane.io ([159.69.161.202]:40874) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j5x1k-0005hY-F4 for emacs-devel@gnu.org; Sun, 23 Feb 2020 14:34:56 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1j5x1g-000HUG-OB for emacs-devel@gnu.org; Sun, 23 Feb 2020 20:34:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 159.69.161.202 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:245047 Archived-At: Eli Zaretskii writes: > Indeed, the byte compiler cannot, which is why issuing a warning is > appropriate. Experience shows that we do pay attention to warnings > and try to have our sources compile warning-free. The less experienced users, which are those who fall the most on the trap (me raises hand) hardly would benefit from a compiler warning. We use regexps on interactive *-regexp commands, not on Elisp code that we later compile. That's package writers.