lex __ wrote: > background: I'm trying to create a 'intelligent' source-code security > analysis tool for c/c++ , python and php files, but filtering the > comments seems to be the biggest problem. :( for C/C++, why not just use "gcc -E source.c" (or equivalent), and use the line markers to figure out what comes from where? </F>