X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: help - export
Date: Wed, 12 Dec 2001 00:19:33 +0000
Lines: 71
Message-ID: <qb8d1u0d272r0ud5bnsf1fv474obr2qu82@4ax.com>
References: <16028921229 DOT 20011207234714 AT go2 DOT pl> <9urha1$51b$2 AT antares DOT lu DOT erisoft DOT se> <Xns917128C42CFrfdfciasdsdj412tr AT 213 DOT 180 DOT 128 DOT 20> <9url94$6l0$1 AT antares DOT lu DOT erisoft DOT se> <8011-Sat08Dec2001100821+0200-eliz AT is DOT elta DOT co DOT il> <Xns917166247666Frfdfciasdsdj412tr AT 213 DOT 180 DOT 128 DOT 20>
NNTP-Posting-Host: modem-41.mississippi.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news7.svr.pol.co.uk 1008116396 1853 62.137.75.41 (12 Dec 2001 00:19:56 GMT)
NNTP-Posting-Date: 12 Dec 2001 00:19:56 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Newsreader: Forte Agent 1.7/32.534
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Raf256 <raf256 AT go2 DOT pl> wrote:

> yes, asy You can see I posted to this group, and to *.c, gnu.gcc.help, and 
> others - and _nobody_ knows how to solve it ?

You are asking the wrong questions.  

Readers in comp.lang.c++ will simply switch off when you talk of compiler
specifics.  Then if you insist there must be be a compiler option to
solve it what do you expect as an answer?  And there will be little joy
asking when the keyword ``export'' will be supported in g++.

> before I thought that DJGPP is best compiler (imho better then VC++), until 
> now... VC++ and even Borland C++ support export (afair), and GCC still 
> doesn't... 

Well I don't use Borland or VC, but somehow I doubt they support the
export keyword either.  Irrelevant anyhow, g++ doesn't support export so
you need a workaround.

> And now nobody can answaer me is it implemented or not ?

GCC does not support the keyword ``export''.

Sorry to rub it in, but IIRC you have been looking for an answer to this
for a long while now and it might help to see why.  Your recent post to
c.l.c++:

}>In help I found long toppic about this, i.e. how to use #pragma interface
}>to solve this problem...
}
}#pragmas are implementation-specific.
}
}>but I don't understand it... maybe somebody more
}>inteligent can PLEASE wite small example ? for YOu it's probably fwe
}>minutes, and for me - I cannot continue my big project without this help :(
}
}You certainly can continue, you just probably cannot use 'export'.
}Do what we all do, put the template stuff in a header.

Like I showed you, in January.

}>btw I don't understand why DJ Delorie didn't yet say anything in this
}>tottic, problems with export is imho biggest problem in DJGPP.
}
}Perhaps M. Delorie is the one to ask about this.  I don't
}think we have any clairvoyants here. :-)
}
}[snip] etc. etc.
}
}All that stuff is specific to that compiler, off-topic here.
}
}If you provide us a small example of code that reproduces
}the problems you report, we can offer better assistance.

There's help on offer, but you will have more luck showing a small
example and asking for a workaround than searching for that magic
compiler option or #pragma.

From my C++ text book here it seems that you should look at explicit
template instantiation.  Like you say:

> which implements that template.  If you don't have any use for a
> particular instance in that file, you can just instantiate it
> explicitly, using the syntax from the latest C++ working paper:
> 
>      template class A<int>;

Now, if there is trouble fitting that into your code, I suggest to post a
_small_ example to comp.lang.c++ and ask for help in using explicit
instantiation.  hint: don't mention gcc, djgpp, or anything like that ;-)