From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Florian Beck Newsgroups: gmane.emacs.help Subject: Re: Byte-compilation warnings Date: Tue, 10 Jun 2008 22:01:54 +0200 Message-ID: <87d4mpcb4d.fsf@sophokles.streitblatt.de> References: <87iqwhcfw6.fsf@sophokles.streitblatt.de> <005c01c8cb2f$2097cd60$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1213128305 19019 80.91.229.12 (10 Jun 2008 20:05:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Jun 2008 20:05:05 +0000 (UTC) Cc: help-gnu-emacs@gnu.org, 'Florian Beck' To: "Drew Adams" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jun 10 22:05:42 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K6A5B-000878-KF for geh-help-gnu-emacs@m.gmane.org; Tue, 10 Jun 2008 22:04:41 +0200 Original-Received: from localhost ([127.0.0.1]:59222 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6A4O-0005EP-F5 for geh-help-gnu-emacs@m.gmane.org; Tue, 10 Jun 2008 16:03:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6A2m-0004ka-Mr for help-gnu-emacs@gnu.org; Tue, 10 Jun 2008 16:02:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6A2j-0004jT-UF for help-gnu-emacs@gnu.org; Tue, 10 Jun 2008 16:02:12 -0400 Original-Received: from [199.232.76.173] (port=56796 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6A2j-0004jM-NE for help-gnu-emacs@gnu.org; Tue, 10 Jun 2008 16:02:09 -0400 Original-Received: from mo-p07-ob.rzone.de ([81.169.146.190]:12826) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6A2j-0005x1-3f for help-gnu-emacs@gnu.org; Tue, 10 Jun 2008 16:02:09 -0400 X-RZG-CLASS-ID: mo07 X-RZG-AUTH: z4gYkBuibEUuEEkKOBbVdyCmH5NHxw== Original-Received: from aeschylus (p54997D48.dip.t-dialin.net [84.153.125.72]) by post.webmailer.de (mrclete mo47) (RZmta 16.42) with ESMTP id K04ea8k5AHBimJ ; Tue, 10 Jun 2008 22:01:56 +0200 (MEST) (envelope-from: ) In-Reply-To: <005c01c8cb2f$2097cd60$0200a8c0@us.oracle.com> (Drew Adams's message of "Tue, 10 Jun 2008 12:21:04 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:54677 Archived-At: "Drew Adams" writes: >> When I byte-compile my elisp files I get lots of warnings=20 >> concerning cl: >>=20 >> Warning: Function `evenp' from cl package called at runtime >>=20 >> I find that annoying because (a) it drowns important warnings=20 >> and (b) it is about a coding convention for packages >> distributed with Emacs that does not concern me at the moment. >> Surely, Emacs maintainers are able to >> determine if something from cl is called at run time without=20 >> spamming the compile log for every user. > > I sympathize with you. > > FWIW, however, I appreciate this warning (information, really) as a user.= I want > to recognize when I might want to either code something differently or use > (eval-when-compile (require 'cl)). Alas, this only works for cl *macros*. If I could repress the faux warnings by some code =E2=80=93 that would be fine. Seems like I cannot. This is really annoying, because it can easily result in *pages* of spurious warnings I *know* to be unwarranted. For me, byte compiler warnings would be a great way to avoid error, would I not tend to ignore them because of the above problems. I can work around `reference to free variable' warnings, but not the cl warnings.=20 The result is not me seriously considering the cl warnings but pretty much disregarding all of them. Not very useful. My point is, I might apprecciate the information *once*, but after that I have made my deciscion. Further warnings only distract me. --=20 Florian Beck, looking for (I-really-want-to-use-cl-even-at-eval)