[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Risky local variable mechanism
From: |
Richard M. Stallman |
Subject: |
Re: Risky local variable mechanism |
Date: |
Wed, 01 Feb 2006 23:17:12 -0500 |
I rarely use file-local variables, so it's hard for me to figure out which
set of restrictions will be best. Using custom types sounds like a good
idea, but note that setting "boolean" variables can be dangerous as well
(e.g. enable-local-eval).
That is a good point--but there are just a few variables which are
dangerous in that way, and they already are marked. The big set of
variables which are dangerous but not marked are those whose values
can be functions to call. That is what I am hoping to recognize using
custom types.
Another idea: just check to see if the value is a function name, or if
any function name (including lambda) appears in it. If so, the value
is risky. That is quite simple and does not depend on knowing the
custom type.
- Re: Risky local variable mechanism, (continued)
- Re: Risky local variable mechanism,
Richard M. Stallman <=
- Re: Risky local variable mechanism, Kim F. Storm, 2006/02/02
- Re: Risky local variable mechanism, Kim F. Storm, 2006/02/02
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/03
- Re: Risky local variable mechanism, Luc Teirlinck, 2006/02/03
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/05
- Re: Risky local variable mechanism, Luc Teirlinck, 2006/02/06
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/07
- Re: Risky local variable mechanism, Luc Teirlinck, 2006/02/06
- Re: Risky local variable mechanism, Chong Yidong, 2006/02/07
- Re: Risky local variable mechanism, Luc Teirlinck, 2006/02/07