duplicate instantiations
Michael Goffioul
michael.goffioul at gmail.com
Tue Jun 2 07:47:52 CDT 2009
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?
If the default visibility is "hidden", does GCC make member classes
visible if the main class is made visible?
Michael.
More information about the Octave-maintainers
mailing list