From: Linas Vepstas <linasvepstas@gmail.com>
To: for.pdv@gmail.com
Cc: guile-user@gnu.org
Subject: Re: Display on guile
Date: Thu, 5 Mar 2009 08:47:11 -0600 [thread overview]
Message-ID: <3ae3aa420903050647y1d65d4ecqc6aaced871d7c963@mail.gmail.com> (raw)
In-Reply-To: <00163646c1e6e017c404645aa0f2@google.com>
2009/3/5 <for.pdv@gmail.com>:
> hi Group,
>
> I executed these commands..
>
> $ guile
> guile> (define mc (cons 'a 'b))
> guile> mc
> (a . b)
> guile> (define ml (list 1 2 mc))
> guile> ml
> (1 2 (a . b))
> guile> (list mc 1 2 3)
> ((a . b) 1 2 3)
> guile> (define mh (make-hash-table 2))
> guile> (hashq-create-handle! mh 'one mc)
> (one a . b)
> guile> (hashq-create-handle! mh 'two ml)
> (two 1 2 (a . b))
> guile> mh
> #(((two 1 2 (a . b)) (one a . b)) ())
> guile> (use-modules (ice-9 pretty-print))
> guile> (pretty-print mh)
> #(((two 1 2 (a . b)) (one a . b)) ())
> guile>
>
> I was expecting handle:'one of hash:mh to be printed in parens as
> #(((two 1 2 (a . b)) (one (a . b))) ())
According to your logic, you must have also been expecting
#(((two (1 2 (a . b))) (one (a . b))) ())
which is not what you wrote.
> Why is behaviour of print for a hash different from others?
> Am I missing anything?
When I read the documentation, I see:
Return the (key . value) pair for key in the given hash table. If key
is not in table then create an entry for it with init as the value,
and return that pair.
Notice the dot between key and value, which means that
hashq-create-handle! behaves like cons, and not like list;
from your mail, it seems that you were expecting it to
behave like list.
--linas
next prev parent reply other threads:[~2009-03-05 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 8:05 Display on guile for.pdv
2009-03-05 14:47 ` Linas Vepstas [this message]
2009-03-05 16:08 ` Praveen D V
2009-03-05 16:11 ` Praveen D V
2009-03-05 18:27 ` Linas Vepstas
2009-03-10 3:41 ` for.pdv
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ae3aa420903050647y1d65d4ecqc6aaced871d7c963@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=for.pdv@gmail.com \
--cc=guile-user@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).