public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mjmaterna60193@yahoo.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/8434: Template Inclusion - keyword 'export' not implemented
Date: Sat, 02 Nov 2002 20:56:00 -0000	[thread overview]
Message-ID: <20021103045001.5868.qmail@sources.redhat.com> (raw)


>Number:         8434
>Category:       c++
>Synopsis:       Template Inclusion - keyword 'export' not implemented
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Nov 02 20:56:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Mark J. Materna
>Release:        2.95.3-216
>Organization:
>Environment:
Linux 
>Description:
Because the keyword export is not yet implemented it seems that I can not have separatley complied template definitions.  Without the key word "export" when a templated class is declared in a .h and defined in a .cpp, when linking the templated class does not seem to be accessable to other translation units. This is expected according to Stroustrup. Is there another way around this?
(Putting the definition in the include is really not ideal because the templated class will be widely used.) I do require this functionality.  

See attached file for an example. The complie command is:
g++ main.cpp matrix.cpp -o matrix
 
>How-To-Repeat:
g++ main.cpp matrix.cpp -o matrix
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-11-03  4:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02 20:56 mjmaterna60193 [this message]
2002-11-02 21:08 zack
2002-11-03  6:16 Gabriel Dos Reis

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=20021103045001.5868.qmail@sources.redhat.com \
    --to=mjmaterna60193@yahoo.com \
    --cc=gcc-gnats@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).