H
Henry Fr?d?ric
I am currently working in Aisin-AW, in development of navigation
systems (embedded SW).
Since a few weeks, we are checking our source code with splint.
We encounter this problem. I hope this mailing-list can help us to
solve
it :
Our team is responsible of 1 module.
In our C files, we include Header files from others modules.
Those files contain splint errors/warnings, but we cannot modify them.
How can we use splint in order to parse those files (necessary for
definitions), but without getting any warning ?
For example, this is not working and we wonder why :
/*@ignore@*/
#include bad_file.h
/*@end@*/
warnings in "bad_file.h" are displayed, anyway.
thank you in advance !
systems (embedded SW).
Since a few weeks, we are checking our source code with splint.
We encounter this problem. I hope this mailing-list can help us to
solve
it :
Our team is responsible of 1 module.
In our C files, we include Header files from others modules.
Those files contain splint errors/warnings, but we cannot modify them.
How can we use splint in order to parse those files (necessary for
definitions), but without getting any warning ?
For example, this is not working and we wonder why :
/*@ignore@*/
#include bad_file.h
/*@end@*/
warnings in "bad_file.h" are displayed, anyway.
thank you in advance !