From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Fixing numerous `message' bugs.. Date: Fri, 07 Dec 2007 19:56:16 -0500 Message-ID: References: <87myso8yrs.fsf@marie.gnufans.net> <87ve7b4xt6.fsf@marie.gnufans.net> <85abonpxnw.fsf@lola.goethe.zz> <85fxyel8o8.fsf@lola.goethe.zz> <87hciugzal.fsf@marie.gnufans.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1197075391 7799 80.91.229.12 (8 Dec 2007 00:56:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 8 Dec 2007 00:56:31 +0000 (UTC) Cc: Dave Goel , rms@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 08 01:56:40 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1J0nzj-0008A5-Tf for ged-emacs-devel@m.gmane.org; Sat, 08 Dec 2007 01:56:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J0nzS-0006bF-SZ for ged-emacs-devel@m.gmane.org; Fri, 07 Dec 2007 19:56:22 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J0nzP-0006aq-As for emacs-devel@gnu.org; Fri, 07 Dec 2007 19:56:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J0nzN-0006aT-RW for emacs-devel@gnu.org; Fri, 07 Dec 2007 19:56:19 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J0nzN-0006aP-NW for emacs-devel@gnu.org; Fri, 07 Dec 2007 19:56:17 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J0nzN-0000xK-If for emacs-devel@gnu.org; Fri, 07 Dec 2007 19:56:17 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1J0nzM-0000X0-Dn; Fri, 07 Dec 2007 19:56:16 -0500 X-Spook: Elvis Mole Peking military red noise Ron Brown digicash X-Ran: r\33?7=Y^HF^0E}A_=7/-FGB"$vaWn (Stefan Monnier's message of "Fri, 07 Dec 2007 13:38:17 -0500") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:84857 Archived-At: Stefan Monnier wrote: > The problem is that all those bugs are here because the corresponding > authors just didn't think, so they are unlikely to use this new > arg either. Is there any way to improve byte-compile-format-warn in this regard? It's easy to make it warn if the first arg to format is not a fixed string or nil, but that leaves false positives for things like: (setq fmt "%s") (message fmt some-variable) Can the byte-compiler figure out what is a known constant at compile time? One would only want it to warn where the first argument is not fully known at compile-time. Because everyone pays attention to compiler warnings, right? ;)