GNU bug report logs - #41983
Reference Manual: Open Question About Magic Metaness of Vtables

Previous Next

Package: guile;

Reported by: sebastian.miele <at> gmail.com

Date: Sun, 21 Jun 2020 14:28:02 UTC

Severity: normal

To reply to this bug, email your comments to 41983 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guile <at> gnu.org:
bug#41983; Package guile. (Sun, 21 Jun 2020 14:28:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to sebastian.miele <at> gmail.com:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Sun, 21 Jun 2020 14:28:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sebastian Miele <sebastian.miele <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: Reference Manual: Open Question About Magic Metaness of Vtables
Date: Sun, 21 Jun 2020 16:27:43 +0200
I am on the current master branch. After reading section 6.6.18.4
(Meta-Vtables) of the reference manual there remains an open question.

A structure X made from a meta-vtable becomes a meta-vtable if
standard-vtable-fields is a prefix of the layout in X's field 0. And if
X is a meta-vtable, every structure with X as a vtable must have a valid
layout in field 0.

Suppose the following: standard-vtable-fields accidentally is a prefix
of some valid layout string l. Then

  (define v (make-vtable l))
  (make-struct/no-tail v 'a)

raises an exception, because 'a is not a valid layout. But v may not be
intended to be a meta-vtable, just a vtable. The reference manual does
mention why that can not happen, or why is it accepted that it may
happen.




This bug report was last modified 3 years and 303 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.