public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7585: Attributes for nested typedef-name ignored Date: Thu, 31 Oct 2002 11:26:00 -0000 [thread overview] Message-ID: <20021031192600.5706.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7585; it has been noted by GNATS. From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/7585: Attributes for nested typedef-name ignored Date: Thu, 31 Oct 2002 19:16:35 +0000 (GMT) On Thu, 31 Oct 2002, Wolfgang Bangerth wrote: > > Said differently, what do you envision for the "right" syntax for > > > > typedef unsigned char type[sizeof(int)] > > __attribute__((__aligned__(__alignof__(int)))); typedef unsigned char (__attribute__((__aligned__(__alignof__(int)))) type)[sizeof(int)] (supposing that the attribute is to be applied to the array type). > I think it would help to have a formal specification of attribute > placement somewhere. Although it would probably be so complicated that > nobody would want to read it... "Attribute Syntax" in the manual. It does presume you fully understand the formal definition in the C standard of declarator syntax, before you can understand how it is extended with attributes. -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2002-10-31 19:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-31 11:26 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-31 9:16 Gabriel Dos Reis 2002-10-31 7:26 Wolfgang Bangerth 2002-10-30 20:16 Gabriel Dos Reis 2002-10-30 16:32 bangerth 2002-08-13 9:36 gdr
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=20021031192600.5706.qmail@sources.redhat.com \ --to=jsm28@cam.ac.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.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: linkBe 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).