From: Josh Triplett <josh@freedesktop.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Improve error message if using a member of an incomplete struct or union
Date: Sat, 09 Jun 2007 00:26:07 -0700 [thread overview]
Message-ID: <466A560F.1000108@freedesktop.org> (raw)
In-Reply-To: <20070605220145.5683.71073.stgit@dv.roinet.com>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
Pavel Roskin wrote:
> sparse should distinguish two cases. One is when the structure or union
> is declared and the member is not found. Another is when the structure
> or union is not yet declared. In the later case, the message should
> indicate that the type is incomplete, rather than complain that the
> particular member is not found.
>
> Mention the incomplete type like gcc does, but provide the member name
> too, it may be useful.
Applied; thanks.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-06-09 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:01 [PATCH] Improve error message if using a member of an incomplete struct or union Pavel Roskin
2007-06-09 7:26 ` Josh Triplett [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=466A560F.1000108@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.