unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "山本和彦 Kazu Yamamoto" <kazu@iij.ad.jp>
Cc: emacs-devel@gnu.org
Subject: Re: unused local variables
Date: Mon, 3 Dec 2007 10:50:04 +0100	[thread overview]
Message-ID: <f7ccd24b0712030150n7f1a6e4cp38ad7091c8134006@mail.gmail.com> (raw)
In-Reply-To: <20071203.113054.70904887.kazu@iij.ad.jp>

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

On Dec 3, 2007 3:30 AM, 山本和彦 Kazu Yamamoto <kazu@iij.ad.jp> wrote:

> To suppress warnings of <3>, there would be two options:
>
> (1) Provide a option to suppress unused local variables (both <2> and
>     <3>). It means that this option does not change Emacs's current
>     behavior.
>
> (2) Prepare a *temporary* defvar for <3> when byte-compiling only for
>    detection purpose. After removing <2>, you can byte-compile without
>    the temporary defvar (and ignoring a warning) and install the elc
>    file.

How will you distinguish between <2> and <3> when my-func1 could be in
another elisp file altogether?

             Juanma

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2007-12-03  9:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 12:32 unused local variables Kazu Yamamoto
2007-11-29 15:31 ` Thien-Thi Nguyen
2007-11-30  0:23   ` Kazu Yamamoto
2007-11-30  9:22     ` Juanma Barranquero
2007-11-30  9:27       ` Kazu Yamamoto
2007-11-30  9:37         ` Juanma Barranquero
2007-11-30  9:59           ` David Kastrup
2007-11-30 10:14             ` Juanma Barranquero
2007-11-30 10:23               ` David Kastrup
2007-11-30 10:26                 ` Juanma Barranquero
2007-11-30 10:36                   ` David Kastrup
2007-11-30 10:49                     ` Juanma Barranquero
2007-11-30 10:34           ` Kazu Yamamoto
2007-11-30 10:45             ` Juanma Barranquero
2007-11-30 11:26               ` David Kastrup
2007-11-30 11:39                 ` Juanma Barranquero
2007-12-03  2:30               ` Kazu Yamamoto
2007-12-03  9:50                 ` Juanma Barranquero [this message]
2007-12-03 10:03                   ` Kazu Yamamoto
2007-11-30 15:10           ` Stefan Monnier
2007-11-30 15:31             ` Juanma Barranquero
2007-11-30 15:58               ` Stefan Monnier
2007-11-30 16:40                 ` David Kastrup
2007-11-30 17:58                   ` tomas
2007-11-30 18:07                 ` Juanma Barranquero
2007-11-30 15:38             ` Juanma Barranquero
2007-11-30 15:59               ` Stefan Monnier
2007-11-30 18:11                 ` Juanma Barranquero
2007-12-01  3:17                   ` Stefan Monnier
2007-11-29 16:02 ` Stefan Monnier
2007-11-30  0:25   ` Kazu Yamamoto
2007-12-04 11:12 ` Katsumi Yamaoka
2007-12-04 15:28   ` Dan Nicolaescu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7ccd24b0712030150n7f1a6e4cp38ad7091c8134006@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kazu@iij.ad.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).