From: Jon Wilson <j85wilson@fastmail.fm>
Subject: Manual revision?
Date: Wed, 27 Sep 2006 14:12:08 -0500 [thread overview]
Message-ID: <451ACD08.2050707@fastmail.fm> (raw)
Hi,
The manual for 1.8, at
"http://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/Symbol-Props.html#index-symbol_002dpset_0021-883",
says the following:
>Support for these extra slots may be removed in a future release, and it
>is probably better to avoid using them. (In release 1.6, Guile itself uses
>the property list slot sparingly, and the function slot not at all.)
My question is, what does guile 1.8 do, and does this need revision?
Regards,
Jon
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2006-09-27 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 19:12 Jon Wilson [this message]
2006-09-27 21:06 ` Manual revision? Neil Jerram
2006-09-27 21:10 ` Jon Wilson
2006-09-28 7:42 ` Neil Jerram
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=451ACD08.2050707@fastmail.fm \
--to=j85wilson@fastmail.fm \
/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).