From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Sat, 29 Feb 2020 17:58:34 -0500 Message-ID: References: <86wo8flqct.fsf@stephe-leake.org> <142e845d-eba3-5975-fa63-4c1b14ed4600@cs.ucla.edu> <3A14F30E-60EF-4C99-AC1A-9A1B2539169B@acm.org> <837e07gmka.fsf@gnu.org> <1c654ac9-10a2-4e5d-f77c-3b78bb580ffc@cs.ucla.edu> <83v9nqg8la.fsf@gnu.org> <298a093f-6eed-3a9f-99cf-bd17b9cb61f0@cs.ucla.edu> <83blpifp95.fsf@gnu.org> <81bfdae0-9fe1-f173-adb1-b5fe2ba2b808@cs.ucla.edu> <834kvafnwk.fsf@gnu.org> <8DA6D8F4-921B-4FB8-A7A3-CE75B10CE668@acm.org> <83zhd2e6h6.fsf@gnu.org> <87k14547u7.fsf@telefonica.net> <87ftet3xo4.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="96299"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: =?windows-1252?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 29 23:59: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 1j8B4x-000Ow8-3U for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Feb 2020 23:59:27 +0100 Original-Received: from localhost ([::1]:36590 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8B4w-0003UC-6D for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Feb 2020 17:59:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36414) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8B4H-0002uS-BQ for emacs-devel@gnu.org; Sat, 29 Feb 2020 17:58:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j8B4F-0002Vu-46 for emacs-devel@gnu.org; Sat, 29 Feb 2020 17:58:44 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:61610) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j8B4E-0002VV-UC for emacs-devel@gnu.org; Sat, 29 Feb 2020 17:58:43 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id F28D38117E; Sat, 29 Feb 2020 17:58:41 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1608980724; Sat, 29 Feb 2020 17:58:36 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1583017116; bh=8Uz+h2YpolqVf9zhfNhKqCwLkNzpZ0HAdqB5Hba3bc4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=f0mVU/aS/5L3M92XNmPMSpsyXA5RGl/7MpNkxb4NWpRbd5HkAYxI/oeHisssvCK51 S+O6pqYHKffi/b0JSmYOjf/Hawl4eAGxuSjPWiHMEhxbOhg9QYMHWRVSOr0Tc2oTO4 YtS2IBHvulkSRQjdoAYC5w+JT2ECWkuHoJs9hVxS/uhiaBZYr+dW2wOnBa+6YkgRes OxfJbMgsHGKRLPdi1JUWAAQ2jcn6cMj6lSAOKrk+sRZxa30vy3QRK03uL6yju/GFla mJ7doQHlJmC26pLEbBaN2+LmSpTMu7xc5YFal+XOBYX+8U24RF4A7LdUp2KbJMjdA4 6A1cW+X4yZdgA== Original-Received: from pastel (unknown [216.154.50.221]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D32C21207A1; Sat, 29 Feb 2020 17:58:35 -0500 (EST) In-Reply-To: <87ftet3xo4.fsf@telefonica.net> (=?windows-1252?Q?=22=D3scar?= Fuentes"'s message of "Sat, 29 Feb 2020 22:12:43 +0100") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 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:245132 Archived-At: > Don't assume that the user compiles his .el files, I don't. I only know that some do, and that compiler warnings reach at least these people. > for starts, implement the warnings on the interpreter too. The interpreter is often not a convenient place since it can't pin point the origin of the code, because adding checks there slows down execution, because in many cases the interpreter doesn't have enough info to perform the needed checks efficiently (e.g. it'd be hard/costly to figure out if a variable is unused), because such warnings will tend to be repeated many many times since the code is likely to be executed many many times, ... (and because it won't catch problems in code that's been compiled ;-). > Show a prompt or prominent notice about the presence of the warnings > (similar to what is shown when the init files has errors). When/where? My best hope for non-compiling authors is that they use tools like flymake which let them see the byte-compiler's warnings even when the user doesn't compile the file. > Ignore files which are likely authored by package writers (a good hint > consists on containing a `provide' or living on certain > directories). On the contrary, these are the people I mostly care to reach. Stefan