From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: deprecating struct permissions?
Date: Sat, 17 Aug 2013 14:20:50 +0200 [thread overview]
Message-ID: <87txio1pb1.fsf@gnu.org> (raw)
In-Reply-To: 874nbokwzz.fsf@pobox.com
Hello!
Andy Wingo <wingo@pobox.com> skribis:
> I would like to deprecate struct permissions.
+1!
[...]
> Finally, struct permissions rely on the struct layout symbol mechanism,
> which is an abomination of an interface. Ideally I'd like to remove
> tail arrays, self fields, opaque fields, read-only fields, and the
> layout symbol in the future, instead replaced by a simple field count
> and bitfield of "raw" values (the "u" fields). So for 2.2 we could have
> all of these features map to "pw" fields, and in 2.4 we could remove
> them entirely. Or we could deprecate them in 2.0 already; dunno.
> Perhaps that is best.
Sounds like a plan. (Tail arrays have been deprecated since 2.0.0 IIRC,
so we could as well remove them in 2.2.)
Another approach would be to keep current structs in parallel with the
new low-level structs, and deprecate them altogether, but that would
create a parallel and incompatible world of structs, so that’s probably
not desirable.
Thanks,
Ludo’.
prev parent reply other threads:[~2013-08-17 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 10:50 deprecating struct permissions? Andy Wingo
2013-08-17 12:20 ` Ludovic Courtès [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=87txio1pb1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).