duplicate instantiations

[Jaroslav Hajek]

On Tue, Jun 2, 2009 at 2:47 PM, Michael Goffioul
<michael.goffioul at gmail.com> wrote:
> On Tue, Jun 2, 2009 at 1:36 PM, Jaroslav Hajek <highegg at gmail.com> wrote:
>> OK, but I'll wait what people on comp.lang.c++ say. It's not a big
>> problem since GCC accepts it
>> (even in -pedantic -ansi, which probably deserves a bug report if I'm
>> right). I'll alert you if I am about to remove these declarations. I
>> was already beginning to think Intel C++ is just barking, but I just
>> tested the online Comeau C++ (on a hopefully equivalent test case),
>> which is reported to be very good at standard conformance diagnostics,
>> and it complains as well :(
>> I'll try to investigate it a bit more. It seems a correct workaround
>> would be to put a whole specialization (including the decorator) into
>> Array-*.cc, but that seems really ugly.
>>
>> Another option is to simply make the instantiations conditional for
>> MSVC. This seems to me the most feasible approach for now.
>
> Did you ever try to play with the visibility attribute of GCC?

No, I didn't. In fact I didn't know about it, so I need to investigate
how it works.
The GCC wiki says that it should reduce the executable size and
possibly speed up loading, which is something that is certainly worth
trying. Thanks for the suggestion.

> If the default visibility is "hidden", does GCC make member classes
> visible if the main class is made visible?
>





-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz