Pelles C > Feature requests

Useful warnings

(1/2) > >>

frankie:
Pelle,
After a very stressing debug last night I would ask you to add two warnings very useful in some cases (in my case sure  :( ).
I get some misterious code malfunction and I could not detect why nevertheless a lot of debug and time. At last I decided to use another compiler, and  :o that it!
The compiler worned me about a "comment extension on next line", due to a code line follwed by a single line comment ending with a backslash:

--- Code: ---......................
a = b      //assign variable \
c = d      //this line is NOT CODED!
result = a * c;    //wrong c not assigned yet
.....................
--- End code ---

the other warning was referred to #if #endif number mismatch.
Could you please add these two warnings to help to avoid frustrating debugs for a so stupid cases?

Thank-you.
F.

Pelle:
Hello Frankie,


--- Quote from: "frankie" ---
The compiler worned me about a "comment extension on next line", due to a code line follwed by a single line comment ending with a backslash:
...

--- End quote ---

OK - I will try to add a warning about this.


--- Quote from: "frankie" ---
the other warning was referred to #if #endif number mismatch.

--- End quote ---

Can you give me an example? Not sure what you mean...

Pelle

frankie:
Thank-you Pelle.
The following should be significative

--- Code: ---
/* file.h */
#ifndef __FILE_H_
#define __FILE_H
#define _a 1
#define ........
.....................................
/* end of file.h - the first #ifndef is not closed with a companion #endif */

--- End code ---


Regards
F.

Pelle:
Mmm... well I do get a level 2 warning for this - "warning #1001: Unterminated conditional in #include."

Pelle

frankie:
Thank-you very much.
I appreciate.
F.

Navigation

[0] Message Index

[#] Next page