public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jadexradex at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/113873] false warning about #pragma once
Date: Sun, 11 Feb 2024 10:32:51 +0000 [thread overview]
Message-ID: <bug-113873-4-3xQoRTXDBV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113873-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113873
--- Comment #4 from Jadex Radex <jadexradex at gmail dot com> ---
(In reply to Sam James from comment #1)
> (In reply to Jadex Radex from comment #0)
> > If you create an empty file with C/C++ extension and write "#pragma once",
> > it will show warning "#pragma once in main file".
> >
>
> What is "it" here? Is it "g++ foo.cxx', or is it 'g++ -c foo.cxx', or
> something else?
Sorry for my ambiguous explanation. I meant the warning inside a code editor
(micro in my case). It doesn't appears at compilation stage.
prev parent reply other threads:[~2024-02-11 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 9:45 [Bug c++/113873] New: " jadexradex at gmail dot com
2024-02-11 9:54 ` [Bug c++/113873] " sjames at gcc dot gnu.org
2024-02-11 10:28 ` [Bug preprocessor/113873] " pinskia at gcc dot gnu.org
2024-02-11 10:28 ` pinskia at gcc dot gnu.org
2024-02-11 10:32 ` jadexradex at gmail dot com [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=bug-113873-4-3xQoRTXDBV@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).