Comment 3 for bug 1086526

If we can't find a way to turn off the diagnostic, the easiest
workaround is probably to change the anonymous namespaces into named
ones. The symbols will be exported, and the compiler won't be able to
tell that the methods aren't used.

Does anybody have opinions about what to do? It's probably easiest to
name the namespaces, but to needlessly export symbols just to please a
picky compiler seems a bit wrong.

On 4 December 2012 22:52, Antony Siahaan <email address hidden> wrote:
> Yes, it is indeed with Intel compiler.
>
> On Dec 4 2012, Joachim Haga wrote:
>
>>Is this with an intel compiler? I suspect it is related to the compiler,
>>not the VTK version.
>>
>>The function is indeed never used, but it is part of the generic VTK
>>class interface. Is there a way to turn off this particular error
>>diagnostic?
>>
>>
>
> --
> You received this bug notification because you are a member of DOLFIN
> Team, which is subscribed to DOLFIN.
> https://bugs.launchpad.net/bugs/1086526
>
> Title:
> Building with VTK-5.10 fails
>
> Status in DOLFIN:
> New
>
> Bug description:
> revno : 7177
>
> Error message :
>
> [ 94%] Building CXX object dolfin/CMakeFiles/dolfin.dir/plot/VTKWindowOutputStage.cpp.o
> ../../dolfin/plot/VTKWindowOutputStage.cpp(83): error #177: function "<unnamed>::PrivateVTKInteractorStyle::NewInstance" was declared but never referenced
> vtkTypeMacro(PrivateVTKInteractorStyle, vtkInteractorStyleTrackballCamera);
> ^
>
> ../../dolfin/plot/VTKWindowOutputStage.cpp(140): error #177: function "<unnamed>::PrivateVTKBalloonWidget::NewInstance" was declared but never referenced
> vtkTypeMacro(PrivateVTKBalloonWidget, vtkBalloonWidget);
> ^
>
> compilation aborted for ../../dolfin/plot/VTKWindowOutputStage.cpp (code 2)
> make[2]: *** [dolfin/CMakeFiles/dolfin.dir/plot/VTKWindowOutputStage.cpp.o] Error 2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dolfin/+bug/1086526/+subscriptions