unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Tassilo Horn <tsdh@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Any disadvantages of using put/get instead of defvar?
Date: Fri, 21 Feb 2014 09:41:00 -0500	[thread overview]
Message-ID: <jwvfvncjzwp.fsf-monnier+INBOX@gnu.org> (raw)
In-Reply-To: <871tywheil.fsf@thinkpad-t61.fritz.box> (Tassilo Horn's message of "Fri, 21 Feb 2014 12:49:22 +0100")

> Sure (I guess you mean with the defvar before the defun), but Oleh's
> goal was not to have the variable and the function separated.

If he wants to keep state between invocations of the function, then that
state has to be external (logically) to the function.  So it is best to
reflect this syntactically by making the variable external as well.

If you want it syntactically "closer", you can put it between the
function's name and the function itself (so it's still outside the
function, but at the same time, it's still within the overall
definition):

  (defalias 'counter
    (let ((counter 1))
      (lambda () (setq counter (1+ counter)))))

Of course, this relies on lexical-binding and is not buffer-local.


        Stefan



  reply	other threads:[~2014-02-21 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 17:04 Any disadvantages of using put/get instead of defvar? Oleh
2014-02-20 22:24 ` Tassilo Horn
2014-02-21  1:40   ` Stefan Monnier
2014-02-21 10:29     ` Nicolas Richard
2014-02-21 13:57       ` Stefan Monnier
2014-02-21 11:49     ` Tassilo Horn
2014-02-21 14:41       ` Stefan Monnier [this message]
2014-02-21  9:12   ` Oleh
2014-02-21  9:39     ` Tassilo Horn
2014-02-21  9:44       ` Oleh
2014-02-21  9:51       ` Andreas Röhler
2014-02-21  9:56         ` Sebastian Wiesner
2014-02-21 11:56         ` Tassilo Horn
     [not found]         ` <mailman.15678.1392983787.10748.help-gnu-emacs@gnu.org>
2014-02-21 13:45           ` Helmut Eller

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=jwvfvncjzwp.fsf-monnier+INBOX@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tsdh@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.
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).