all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Kazu Yamamoto" <kazu@iij.ad.jp>
To: emacs-devel@gnu.org
Subject: Re: unused local variables
Date: Mon, 03 Dec 2007 11:30:54 +0900 (JST)	[thread overview]
Message-ID: <20071203.113054.70904887.kazu@iij.ad.jp> (raw)
In-Reply-To: <f7ccd24b0711300245u4ff38350i3bae3623fdc4d5ab@mail.gmail.com>

Hello,

> What I want to say is that case-fold-search in the following example
> > is not warned with XEmacs because it is defined with 'defvar'.
> 
> So, yes: what you propose is forcing `defvar' for dynamic variables
> used across function boundaries.

Probaby you misunderstood. I did not use the word "force".

Let me explain the whole story:

----
(defvar my-global-var nil)

(defun my-func1 ()
  (setq my-local-inherit-var (1+ my-local-inherit-var)))

(defun my-func()
  (let ((my-global-var t)         ;; <1>
	(my-local-var 1)          ;; <2>
	(my-local-inherit-var 2)) ;; <3>
    ;; code which does not refer these three variabls above
    (my-func1)
    ))
----

My purpose is to detect <2>.

XEmacs warns both <2> and <3>. I said this is good enough because
I can find <2>.

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.

--Kazu

  parent reply	other threads:[~2007-12-03  2:30 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 [this message]
2007-12-03  9:50                 ` Juanma Barranquero
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

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

  git send-email \
    --in-reply-to=20071203.113054.70904887.kazu@iij.ad.jp \
    --to=kazu@iij.ad.jp \
    --cc=emacs-devel@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.