From: Joseph Myers <josmyers@redhat.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: "richard.guenther@gmail.com" <richard.guenther@gmail.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
"uecker@tugraz.at" <uecker@tugraz.at>,
Kees Cook <keescook@chromium.org>,
"isanbard@gmail.com" <isanbard@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v7 1/5] Provide counted_by attribute to flexible array member field (PR108896)
Date: Tue, 26 Mar 2024 15:21:08 +0000 (UTC) [thread overview]
Message-ID: <472cd-223e-91bd-a7bd-70ba6eaefaf3@redhat.com> (raw)
In-Reply-To: <932CCEBB-8107-4347-B94B-8F96E9CD8938@oracle.com>
On Tue, 26 Mar 2024, Qing Zhao wrote:
> >> +@cindex @code{counted_by} variable attribute
> >> +@item counted_by (@var{count})
> >> +The @code{counted_by} attribute may be attached to the C99 flexible array
> >> +member of a structure. It indicates that the number of the elements of the
> >> +array is given by the field named "@var{count}" in the same structure as the
> >> +flexible array member.
> >
> > You shouldn't use ASCII quotes like that in Texinfo (outside @code etc.
> > where they represent literal quotes in programming language source code).
> > You can say ``@var{count}'' if you wish to quote the name.
> A little confused with the above..
> So, what should I change in the above statement?
I don't think you actually need quotes (or "named") at all; just
the field @var{count}
in place of
the field named "@var{count}"
would suffice. But if you use quotes (for an English-language quotation,
as opposed to when the quotes themselves are part of programming-language
source code given in the manual), in Texinfo you should use ``'' rather
than "".
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2024-03-26 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 13:15 [PATCH v7 0/5] New attribute "counted_by" to annotate bounds for C99 FAM(PR108896) Qing Zhao
2024-03-20 13:15 ` [PATCH v7 1/5] Provide counted_by attribute to flexible array member field (PR108896) Qing Zhao
2024-03-25 20:44 ` Joseph Myers
2024-03-26 15:11 ` Qing Zhao
2024-03-26 15:21 ` Joseph Myers [this message]
2024-03-26 16:01 ` Qing Zhao
2024-03-26 17:20 ` Joseph Myers
2024-03-27 20:40 ` Qing Zhao
2024-03-20 13:15 ` [PATCH v7 2/5] Convert references with "counted_by" attributes to/from .ACCESS_WITH_SIZE Qing Zhao
2024-03-25 20:48 ` Joseph Myers
2024-03-26 15:13 ` Qing Zhao
2024-03-20 13:15 ` [PATCH v7 3/5] Use the .ACCESS_WITH_SIZE in builtin object size Qing Zhao
2024-03-25 20:50 ` Joseph Myers
2024-03-26 15:14 ` Qing Zhao
2024-03-20 13:15 ` [PATCH v7 4/5] Use the .ACCESS_WITH_SIZE in bound sanitizer Qing Zhao
2024-03-20 13:15 ` [PATCH v7 5/5] Add the 6th argument to .ACCESS_WITH_SIZE Qing Zhao
2024-03-20 19:07 ` [PATCH v7 0/5] New attribute "counted_by" to annotate bounds for C99 FAM(PR108896) Kees Cook
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=472cd-223e-91bd-a7bd-70ba6eaefaf3@redhat.com \
--to=josmyers@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=isanbard@gmail.com \
--cc=keescook@chromium.org \
--cc=qing.zhao@oracle.com \
--cc=richard.guenther@gmail.com \
--cc=siddhesh@gotplt.org \
--cc=uecker@tugraz.at \
/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).