I use sparse in a cygwin environment to obtain pre-build info from sourcefiles which get comiled with gcc (also compiled with cygwin).
After some time of using sparse, I noticed some differences in the behaviour of sparse and gcc: 1. Symbolnames with "$" are accepted by gcc but not by sparse 2. #include "..\plc.h" is accepted by gcc but not by sparse => "\" is interpreted as escape- character 3. #include "D:\plc.h" is accepted by gcc but not by sparse I know that number 2 and 3 are problems which only occur within an cygwin environment and number 3 isn't the best way to include files, but is there any chance to get this fixed? Best regards, Thomas Schmid - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
