From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ISO C and typestr
Date: Fri, 15 Mar 2013 13:09:13 -0400 [thread overview]
Message-ID: <CAFUtaNGvtD+2X9aoHW8NWRyfh2u4jPfmy50ssvshq983FJbGww@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5jfUXv4hWn0VRoe1c4XCtVu+2VrPmtgZ3kNKPNtLbTPzg@mail.gmail.com>
On Fri, Mar 15, 2013 at 1:01 PM, Charles Forsyth
<charles.forsyth@gmail.com> wrote:
> On 15 March 2013 16:52, Joel C. Salomon <joelcsalomon@gmail.com> wrote:
>> BTW, the C11 standard includes a restricted form of 9c's anonymous
>> sub-structs (with no pointer conversion).
>
> isn't the pointer conversion most of the point of them?
Given this code:
typedef struct Foo Foo;
struct Foo {
int flag;
Lock;
} *foo;
C11 allows you to write `lock(foo->Lock)`, or to directly access named
members of `struct Lock` as if they were members of `struct Foo`. An
early draft of the feature did allow `lock(foo)`, but that was
rejected (I don't know why).
—Joel
prev parent reply other threads:[~2013-03-15 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 16:52 Joel C. Salomon
2013-03-15 17:01 ` Charles Forsyth
2013-03-15 17:09 ` Joel C. Salomon [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFUtaNGvtD+2X9aoHW8NWRyfh2u4jPfmy50ssvshq983FJbGww@mail.gmail.com \
--to=joelcsalomon@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).