From:	dontmailme AT iname DOT com (Steamer)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Authors of DJGPP / GCC - #export needed !
Date:	Sun, 21 Jan 2001 13:51:50 GMT
Organization:	always disorganized
Lines:	31
Message-ID:	<3a6ae96b.11323719@news.freeserve.net>
References:	<94ejfb$5a5$1 AT info DOT cyf-kr DOT edu DOT pl>
NNTP-Posting-Host:	modem-243.nebraska.dialup.pol.co.uk
X-Trace:	news6.svr.pol.co.uk 980085111 17023 62.137.78.243 (21 Jan 2001 13:51:51 GMT)
NNTP-Posting-Date:	21 Jan 2001 13:51:51 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Newsreader:	Forte Free Agent 1.11/32.235
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Rafal Maj wrote:

> When #export will be implemented in DJGPP ?  Next month :), maybe next year
> :(  ?

You mean the 'export' keyword.  I heard recently that this is being
worked on for GCC.  But don't expect it soon - it's not exactly trivial...

This problem is not exclusive to GCC.  In fact, there is currently not
a single C++ compiler in existence that supports 'export'.

> I'm stuck because my program realy needs to use template class in libraries
> and now I'm waiting for this #export keyword...

You can't _really_ need 'export'.  Just put the templates in a
header file.

> By the way... why is it realy so incredibly hard to implement ?

Think about what it has to do.  How do you compile a template?
Clearly you can't compile it to machine code.  So maybe you compile
it to some binary representation of the template.  But what is the
linker supposed to do with this binary representation?  Doesn't it
need to know pretty much the whole of the C++ language in order to
handle it?

> Maybe writting future-request directly to authors of GCC may help... do
> somebody know their email ?

As I said, they appear to be working on it.  And even if they weren't
working on it, they would already know that it needs to be done.

- Raw text -