From: Sebastian Miele <sebastian.miele@gmail.com>
To: 41981@debbugs.gnu.org
Subject: bug#41981: Reference Manual on Vtables: Missing Information on Permission "h"
Date: Sun, 21 Jun 2020 15:51:42 +0200 [thread overview]
Message-ID: <87h7v4o7bl.fsf@gmail.com> (raw)
I am on the current master branch. The standard-vtable-fields is
"pwuhuhpwphuhuhuh" on my system and something similar in the Reference
Manual. In particular, it contains the permission letter "h", but I find
no explanation in the manual what that means.
Section 6.6.18.1 (Vtables) just mentions: "It used to be that the second
letter for each field was a permission code, such as ‘w’ for writable or
‘r’ for read-only." And that read-only has become depriciated.
At the end of section 6.6.18.4 (Meta-Vtables) is an example:
(define* (make-vtable fields #:optional printer)
(make-struct/no-tail <standard-vtable>
(make-struct-layout fields)
printer))
Without information on "h", I was not able to make sense of the fact,
that fields with permission "h" somehow seem to be skipped by
make-struct/no-tail when processing the two init values. In particular,
for some reason, the value of printer is put into field 3 of the new
structure and not in field 1, almost certainly somehow because fields 1
and 2 have "h".
"h" should be documented.
next reply other threads:[~2020-06-21 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 13:51 Sebastian Miele [this message]
2020-06-21 16:29 ` bug#41981: Reference Manual on Vtables: Missing Information on Permission "h" dsmich
2020-06-22 13:42 ` Sebastian Miele
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=87h7v4o7bl.fsf@gmail.com \
--to=sebastian.miele@gmail.com \
--cc=41981@debbugs.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).