www.delorie.com/archives/browse.cgi | search |
From: | Nate Eldredge <neldredge AT hmc DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Authors of DJGPP / GCC - #export needed ! |
Date: | 22 Jan 2001 09:53:53 -0800 |
Organization: | InterWorld Communications |
Lines: | 44 |
Sender: | nate AT mercury DOT st DOT hmc DOT edu |
Message-ID: | <83hf2rqxqm.fsf@mercury.st.hmc.edu> |
References: | <Pine DOT LNX DOT 4 DOT 30 DOT 0101230644160 DOT 546-100000 AT anthony DOT siemens DOT ebp DOT ii3 DOT b-rail DOT be> |
NNTP-Posting-Host: | mercury.st.hmc.edu |
Mime-Version: | 1.0 |
X-Trace: | nntp1.interworld.net 980186034 63246 134.173.57.219 (22 Jan 2001 17:53:54 GMT) |
X-Complaints-To: | usenet AT news DOT interworld DOT net |
NNTP-Posting-Date: | Mon, 22 Jan 2001 17:53:54 +0000 (UTC) |
User-Agent: | Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Dieter Demerre <ext DOT dieter DOT demerre AT siemens DOT be> writes: > On Mon, 22 Jan 2001, Andris Pavenis wrote: > > > On Sun, 21 Jan 2001, Rafal Maj wrote: > > > > > When #export will be implemented in DJGPP ? Next month :), maybe next year > > > :( ? > > > I'm stuck because my program realy needs to use template class in libraries > > > and now I'm waiting for this #export keyword... > > > By the way... why is it realy so incredibly hard to implement ? > > > Maybe writting future-request directly to authors of GCC may help... do > > > somebody know their email ? > > > Rafał > > > > I think no one will be able to answer You now. It will be supported when > > GCC will support it. Currently it's not in development version of gcc and > > there are no plans for it in nearest future AFAIK. For more info go to > > http://gcc.gnu.org and search gcc related mailing lists for this topic ... > > Can anybody direct me to information about this #export directive ? I > consulted the C++-primer and couldn't find anything about it. Are you > (Rafal) sure it's part of any standard ? An `export' (not `#export') keyword is described in Stroustrup 4ed section 13.7. It's intended to work like the following: foo.h: template<class T> void foo (const T&); foo.cc: #include "foo.h" export template<class T> void foo (const T& arg) { ... } So maybe this is what the original poster has in mind. AFAIK, this feature is hard to implement because it requires a fair amount of magic in both the compiler and linker. See also the node "Template Instantiation" in the GCC docs. -- Nate Eldredge neldredge AT hmc DOT edu
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |