public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8434: Template Inclusion - keyword 'export' not implemented
Date: Sun, 03 Nov 2002 06:16:00 -0000 [thread overview]
Message-ID: <20021103141600.27104.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/8434; it has been noted by GNATS.
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: mjmaterna60193@yahoo.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/8434: Template Inclusion - keyword 'export' not implemented
Date: 03 Nov 2002 15:13:48 +0100
mjmaterna60193@yahoo.com writes:
| >Synopsis: Template Inclusion - keyword 'export' not implemented
[...]
| >Class: sw-bug
This is not a bug in the compiler. It is known that GCC has (not yet)
no plan to implement "export", and a diagnostic is emitted when an
attempt is made to use that keyword.
[...]
| Is there another way around this?
Make your template definitions available to the compiler when
instantiating -- the easiest way is to put the template code in a
header file.
| (Putting the definition in the include is really not ideal because
| the templated class will be widely used.)
It is however a *practical* solution.
| I do require this functionality.
Well, GCC is a volunteer project; you cannot *require*.
-- Gaby
next reply other threads:[~2002-11-03 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 6:16 Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 21:08 zack
2002-11-02 20:56 mjmaterna60193
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=20021103141600.27104.qmail@sources.redhat.com \
--to=gdr@integrable-solutions.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).