unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Sebastian Miele <sebastian.miele@gmail.com>
To: dsmich@roadrunner.com
Cc: "'41981@debbugs.gnu.org'" <41981@debbugs.gnu.org>
Subject: bug#41981: Reference Manual on Vtables: Missing Information on Permission "h"
Date: Mon, 22 Jun 2020 15:42:46 +0200	[thread overview]
Message-ID: <877dvzkyi1.fsf@gmail.com> (raw)
In-Reply-To: <e1278f5af69d8dafacd1fc054ff5d0847ad3d65a@webmail>

dsmich@roadrunner.com writes:
> Is is documented in the docstring:
>
> scheme@(guile-user)> ,d make-struct-layout

In the reference manual, a description of make-struct-layout directly
precedes the '(define* (make-vtable ..) ..)' example that cannot be
understood without somehow grasping what is documented about "h" in the
docstring of make-struct-layout. However, the description of
make-struct-layout in the reference manual says: "FIELDS is as described
under ‘make-vtable’ (*note Vtables::)". But that description lacks the
information on "h".

It may be a matter of opinion. But my opinion stronly is that
descriptions about the behavior around permission "h" do should appear
in the reference manual in two places: The description of make-vtable
and the description of make-struct/no-tail.

After glancing at libguile/struct.c, "w", "h", and the depreciated "r"
seem in fact to be all possible permissions. I will prepare a patch after
I finish getting a good overview of Guile.





      reply	other threads:[~2020-06-22 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 13:51 bug#41981: Reference Manual on Vtables: Missing Information on Permission "h" Sebastian Miele
2020-06-21 16:29 ` dsmich
2020-06-22 13:42   ` Sebastian Miele [this message]

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=877dvzkyi1.fsf@gmail.com \
    --to=sebastian.miele@gmail.com \
    --cc=41981@debbugs.gnu.org \
    --cc=dsmich@roadrunner.com \
    /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).