unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Hannes Müller" <h.c.f.mueller@gmail.com>
To: 40780@debbugs.gnu.org
Subject: bug#40780: guile 3.0.4: #40780 can be closed (typedef redefinition allowed in c11)
Date: Sat, 05 Dec 2020 12:25:25 +0100	[thread overview]
Message-ID: <d8d27ac3a823ce8fcfeeeb02c780e8bb88a01f6a.camel@gmail.com> (raw)
In-Reply-To: <a583e645c4018b316845fadd86a07179fabf048f.camel@gmail.com>

Dear Maintainer,

I consider this bug report can be closed.

The 2011 C standard allows redeclaration of typedef names. 6.7 3 says:
… a typedef name may be redefined to denote the same type as it
currently does, provided that type is not a variably modified type;…

I compiled my application with -std=c11 and -Wpedantic using libguile
3.0.4: no warning is shown any more. 

Thanks!
Hannes






      reply	other threads:[~2020-12-05 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 19:30 bug#40780: guile 3.0.2: Prevent warning using libguile with -Wpedantic (redefinition) Hannes Müller
2020-12-05 11:25 ` Hannes Müller [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=d8d27ac3a823ce8fcfeeeb02c780e8bb88a01f6a.camel@gmail.com \
    --to=h.c.f.mueller@gmail.com \
    --cc=40780@debbugs.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).