public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/8434: Template Inclusion - keyword 'export' not implemented
@ 2002-11-02 21:08 zack
  0 siblings, 0 replies; 3+ messages in thread
From: zack @ 2002-11-02 21:08 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, mjmaterna60193, nobody

Synopsis: Template Inclusion - keyword 'export' not implemented

State-Changed-From-To: open->closed
State-Changed-By: zack
State-Changed-When: Sat Nov  2 21:08:07 2002
State-Changed-Why:
    Duplicate of 8435, which has more information.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8434


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c++/8434: Template Inclusion - keyword 'export' not implemented
@ 2002-11-03  6:16 Gabriel Dos Reis
  0 siblings, 0 replies; 3+ messages in thread
From: Gabriel Dos Reis @ 2002-11-03  6:16 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* c++/8434: Template Inclusion - keyword 'export' not implemented
@ 2002-11-02 20:56 mjmaterna60193
  0 siblings, 0 replies; 3+ messages in thread
From: mjmaterna60193 @ 2002-11-02 20:56 UTC (permalink / raw)
  To: gcc-gnats


>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:


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-11-03 14:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-11-02 21:08 c++/8434: Template Inclusion - keyword 'export' not implemented zack
  -- strict thread matches above, loose matches on Subject: below --
2002-11-03  6:16 Gabriel Dos Reis
2002-11-02 20:56 mjmaterna60193

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).