>
>
> Sorry to say to say that it is /easy/ to use and it just works.
>
Having cake.

> That is actually difficult to asses as long as it is yet
> hardly implemented.
>
Eating cake.

You cannot have your cake and eat it too.  Either export is hardly
implemented, in which case you cannot truthfully state that it is "easy
to use and just works", or it is widely and fully implemented so that
indeed it "just works", and lack of demand for it is not "difficult to
assess" at all.

--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

On Jan 30, 6:04 pm, Jonathan de Boyne Pollard <J.deBoynePollard-
newsgro...@NTLWorld.COM> wrote:
> > Sorry to say to say that it is /easy/ to use and it just works.
>
> Having cake.
>
> > That is actually difficult to asses as long as it is yet
> > hardly implemented.
>
> Eating cake.
>
> You cannot have your cake and eat it too.  Either export is hardly
> implemented, in which case you cannot truthfully state that it is "easy
> to use and just works" [...]
[...]

To use export you write the keyword in front of the template
declaration, then you can write the template definition in a separate
source (.cc or .cpp) file.

Until compilers support export, you an also resort to the easy trick
with the USE_EXPORT #define presented for example in "C++ Templates:
The complete guide"; you will like it. To help with it, most compilers
can even ignore export keyword (with a warning).

Thank you,
Timothy Madden


--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]