public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pilarlatiesa at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102341] [modules] "error: conflicting exporting declaration" for anything previously declared Date: Wed, 15 Sep 2021 11:37:24 +0000 [thread overview] Message-ID: <bug-102341-4-r1xSEokqmM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102341-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102341 Pilar Latiesa <pilarlatiesa at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pilarlatiesa at gmail dot com --- Comment #4 from Pilar Latiesa <pilarlatiesa at gmail dot com> --- In PR98885#C1 Nathan said that "an exported entity must be so-declared on its first declaration". Would it be possible to forward-declare every exported entity and then `#include`ing all the headers? I mean something along the lines: $ cat borrar.h namespace Test { template<typename T> class valarray {}; } $ cat borrar.cpp export module Test; namespace Test { export template<typename T> class valarray; } #include "borrar.h" $ cat main.cpp import Test; int main() { Test::valarray<double> v; return 0; } $ g++-11 -Wall -Wextra -fmodules-ts borrar.cpp main.cpp main.cpp: In function ‘int main()’: main.cpp:6:26: warning: unused variable ‘v’ [-Wunused-variable] 6 | Test::valarray<double> v; | ^ However, I don't think that this approach can be used to split the library into several modules.
next prev parent reply other threads:[~2021-09-15 11:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 9:46 [Bug c++/102341] New: [modules] alias-declaration and typedef-declaration conflict in module interface unit redi at gcc dot gnu.org 2021-09-15 9:52 ` [Bug c++/102341] " redi at gcc dot gnu.org 2021-09-15 10:34 ` redi at gcc dot gnu.org 2021-09-15 11:28 ` [Bug c++/102341] [modules] "error: conflicting exporting declaration" for anything previously declared redi at gcc dot gnu.org 2021-09-15 11:37 ` pilarlatiesa at gmail dot com [this message] 2021-09-15 11:50 ` redi at gcc dot gnu.org 2023-11-25 1:45 ` cvs-commit at gcc dot gnu.org
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-102341-4-r1xSEokqmM@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: 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).