At 02:44 AM 8/15/2006, Arjen Markus wrote:
>> worked out?
>
>Please reduce that to:
>
>^[cC*].*\n { return EOSTMT; }
>
>and you will not miss any dependencies as far as I can tell.
>
>(I was wondering about false positives, like when you have
>"INCLUDE 'filename'" or "USE module" in a literal string,
>but it should be relatively easy to detect them. The following
>fragment could cause a false dependency:I have checked in the above: Checking for path: /cvsroot/CMake/CMake/Source Unrestricted user: hoffman /cvsroot/CMake/CMake/Source/cmDependsFortranLexer.cxx,v <-- cmDependsFortranLexer.cxx new revision: 1.8; previous revision: 1.7 /cvsroot/CMake/CMake/Source/cmDependsFortranLexer.h,v <-- cmDependsFortranLexer.h new revision: 1.4; previous revision: 1.3 /cvsroot/CMake/CMake/Source/cmDependsFortranLexer.in.l,v <-- cmDependsFortranLexer.in.l new revision: 1.8; previous revision: 1.7 Please try cvs cmake, and tell me if it fixes your problems with fortran depends. Thanks. -Bill _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
