From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: lexbind: how to replace lexical-let approach to hide secrets (was: lexbind ready for merge)
Date: Wed, 30 Mar 2011 08:24:46 -0500 [thread overview]
Message-ID: <87lizwd9lt.fsf_-_@lifelogs.com> (raw)
In-Reply-To: AANLkTinSARJP8ofq3bqQvKXr9q_Qr7amW=D66hVbPQ0a@mail.gmail.com
On Wed, 30 Mar 2011 13:35:56 +0200 Juanma Barranquero <lekktu@gmail.com> wrote:
JB> On Wed, Mar 30, 2011 at 06:10, Daniel Colascione
JB> <dan.colascione@gmail.com> wrote:
>> Even if it's not particularly common, being consistent with Common Lisp and
>> having fewer special cases are good things. Some people use constructs like
>> this to create module-private variables (which is a bad idea, but that
>> doesn't stop people doing it.)
JB> Why a bad idea? It's a common idiom for private, persistent variables.
Slightly related: auth-source.el uses `lexical-let' to define lambda
accessors for secrets (so printing them, for instance, won't show a
password). Will the secrets still be hidden in the lexbind branch? And
is there a smarter way to do it?
Sample code:
(let ((data "my secret"))
(lexical-let ((data data)) (lambda () data)))
Thanks
Ted
next prev parent reply other threads:[~2011-03-30 13:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 21:44 lexbind ready for merge Stefan Monnier
2011-03-29 23:43 ` Daniel Colascione
2011-03-30 1:22 ` Stefan Monnier
2011-03-30 4:10 ` Daniel Colascione
2011-03-30 11:35 ` Juanma Barranquero
2011-03-30 13:24 ` Ted Zlatanov [this message]
2011-03-30 21:12 ` lexbind: how to replace lexical-let approach to hide secrets Stefan Monnier
2011-03-30 21:56 ` David Kastrup
2011-03-30 22:29 ` Daniel Colascione
2011-03-31 15:42 ` Ted Zlatanov
2011-04-01 1:31 ` Stephen J. Turnbull
2011-04-01 4:41 ` secret strings (was: lexbind: how to replace lexical-let approach to hide secrets) Ted Zlatanov
2011-04-01 5:52 ` Stephen J. Turnbull
2011-04-01 11:02 ` secret strings Ted Zlatanov
2011-04-01 14:38 ` Stephen J. Turnbull
2011-04-01 15:12 ` Ted Zlatanov
2011-04-01 16:14 ` Stephen J. Turnbull
2011-04-01 20:08 ` Ted Zlatanov
2011-04-01 20:34 ` Stefan Monnier
2011-04-01 21:25 ` Ted Zlatanov
2011-04-01 14:59 ` Stefan Monnier
2011-03-30 15:09 ` lexbind ready for merge Daniel Colascione
2011-03-30 15:20 ` Juanma Barranquero
2011-03-30 14:26 ` Stefan Monnier
2011-03-30 7:28 ` Tassilo Horn
2011-03-30 11:30 ` Eli Zaretskii
2011-03-30 13:10 ` Tassilo Horn
2011-03-30 13:17 ` Ted Zlatanov
2011-03-30 14:29 ` Stefan Monnier
2011-03-30 14:54 ` Tassilo Horn
2011-03-31 1:02 ` Stephen J. Turnbull
2011-03-30 16:11 ` Lars Magne Ingebrigtsen
2011-03-30 17:10 ` Tassilo Horn
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=87lizwd9lt.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--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.