LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Compiler BUG ?

I've seen that when you put a line in comments and when that line is ended
by the character '\' to say that it's follows next line, you've got a pb
during compilation.
Here's an example that doesn't work :

//#define sFIELDS "Field1,Field2"\
#define sFIELDS "Field1"\
",Field3,Field4"
0 Kudos
Message 1 of 2
(2,868 Views)
The question is whether the comment or the line continuation takes
precedence. I've tried this piece of code in both Microsoft VC++ and
Borland C++ 4.52 and their behavior is the same as ours i.e. all three
lines are commented and nothing is #define'd.

However, CVI's syntax coloring doesn't recognize this case, unlike
VC's, and so it appears as if the second and third line will be read
by the preprocessor. VC also issues warnings about line continuations
in single-line comments.

While we won't change the current behavior to avoid compatibility
problems, I'll add suggestions to fix these two items (syntax
coloring, warnings).

Peter

-- Peter Ilberg

"Pierre DURIEZ" writes:
> I've seen that when you put a
line in comments and when that line is ended
> by the character '\' to say that it's follows next line, you've got a pb
> during compilation.
> Here's an example that doesn't work :
>
> //#define sFIELDS "Field1,Field2"\
> #define sFIELDS "Field1"\
> ",Field3,Field4"
0 Kudos
Message 2 of 2
(2,868 Views)