My 2 cents would be that I think a good coding practice is to define these in your source file instead of the header. Especially as it they doesn't appear to be part of your API. Or even better is to make them const variables. That way it will actually exist as a symbol that you can see in a debugger and, I think, optimizations can be performed.
On Wed, Mar 10, 2010 at 10:15 AM, David Doria <daviddo...@gmail.com> wrote: > On Fri, Mar 5, 2010 at 10:04 AM, David Doria <daviddo...@gmail.com> wrote: > >> I am getting this error when building a plugin: >> >> SYNTAX ERROR found in parsing the header file >> >> I finally remembered to try BTX ETX tags, but they didn't work this time: >> >> The header is very simple, here is a representative sample: >> >> #ifndef FACTOR_INCLUDED >> #define FACTOR_INCLUDED >> //BTX >> #define SQRT_3 1.7320508075688772935 >> >> double ArcTan2(const double& y,const double& x); >> >> //ETX >> #endif // FACTOR_INCLUDED >> >> Is there any reason the parser wouldn't like this? >> >> Thanks, >> >> David >> >> > Here is the simplest example that demonstrates the problem: > http://rpi.edu/~doriad/Paraview_List/TestClass.zip > > Thanks, > > David > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
