From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: hash strangeness
Date: Sun, 02 Nov 2014 19:43:25 +0100 [thread overview]
Message-ID: <87k33d30ky.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: mailman.12577.1414927271.1147.help-gnu-emacs@gnu.org
Tom <adatgyujto@gmail.com> writes:
> Here's a code which gives me some headache. It's silly, because
> it was shortened from a longer code to demonstrate the problem.
>
> It is supposed to count something in elisp functions, though
> the condition is removed, so with this code the count should be
> 1 for every function.
>
> So the code checks if the function is already in the hash
> and if not then it inserts new info for that function:
>
>
> (let ((h (make-hash-table :test 'equal)))
> (mapatoms
> (lambda (s)
> (let* ((name (symbol-name s))
> (info (gethash name h)))
>
> (unless info
> (setq info '(count 0)))
>
> (setq info (plist-put info
> 'count (1+ (plist-get info 'count))))
>
> (puthash name info h))))
>
> (pop-to-buffer "*testout*")
> (erase-buffer)
> (maphash (lambda (name info)
> (insert (format "%s %s" (plist-get info 'count) name) "\n"))
> h))
>
>
> The new info is newly created in the lambda function (it is
> a plist, because in the real code there are other fields too),
> yet for some reason the same info structure is used for all
> iterations.
>
> I tried to debug it and at the "(unless info" part info is nil
> and then it is set to the previous value, though it should be a
> new value.
>
> Am I missing something here?
You've identified the problem with the literal list. However, you could
write it much simplier:
(require 'cl) ; always
(let ((h (make-hash-table :test 'eql)))
(mapatoms (lambda (name)
(incf (getf (gethash name h) 'count 0))))
(pop-to-buffer "*testout*")
(erase-buffer)
(maphash (lambda (name info)
(insert (format "%s %s\n" (getf info 'count) name)))
h))
In the current emacs lisp, there's no point in using symbol-name strings
as key in the hash-table: just use symbols with eql as test.
Notice that in emacs lisp:
(not (equal (symbol-name :hello) (symbol-name 'hello)))
It would be different if emacs lisp had packages like Common Lisp.
--
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
next parent reply other threads:[~2014-11-02 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12577.1414927271.1147.help-gnu-emacs@gnu.org>
2014-11-02 18:43 ` Pascal J. Bourguignon [this message]
2014-11-02 20:48 ` hash strangeness Tom
2014-11-02 11:20 Tom
2014-11-02 12:09 ` Tom
2014-11-02 18:20 ` Thien-Thi Nguyen
2014-11-02 20:45 ` Tom
[not found] ` <mailman.12618.1414961152.1147.help-gnu-emacs@gnu.org>
2014-11-02 22:25 ` Pascal J. Bourguignon
2014-11-02 22:48 ` Barry Margolin
2014-11-03 21:29 ` Tom
2014-11-04 1:57 ` Robert Thorpe
2014-11-04 2:16 ` Michael Heerdegen
[not found] ` <<barmar-14233C.17480902112014@88-209-239-213.giganet.hu>
2014-11-04 3:04 ` Drew Adams
2014-11-04 7:39 ` Marcin Borkowski
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=87k33d30ky.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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).