[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strange byte compiler behavior
|
From: |
Richard Stallman |
|
Subject: |
Re: strange byte compiler behavior |
|
Date: |
Sun, 06 Jan 2008 13:09:23 -0500 |
They are, but elsewhere and the byte-compiler only knows about it via
`boundp': it doesn't keep its own list of defvar'd variables.
Indeed, that is true. But we COULD make it check for a variable doc
string instead.
The effect would be that variables defvar'd in another file with no
doc string would get warnings. Maybe that is not a bad result.
- Re: strange byte compiler behavior, (continued)
- Re: strange byte compiler behavior, Dan Nicolaescu, 2008/01/02
- Re: strange byte compiler behavior, martin rudalics, 2008/01/02
- Re: strange byte compiler behavior, Dan Nicolaescu, 2008/01/02
- Re: strange byte compiler behavior, David Kastrup, 2008/01/02
- Re: strange byte compiler behavior, Richard Stallman, 2008/01/04
- Re: strange byte compiler behavior, Stefan Monnier, 2008/01/04
- Re: strange byte compiler behavior, Richard Stallman, 2008/01/05
- Re: strange byte compiler behavior, Stefan Monnier, 2008/01/05
- Re: strange byte compiler behavior, martin rudalics, 2008/01/06
- Re: strange byte compiler behavior,
Richard Stallman <=