search for: bad_funct

...able names aside from the fact it can't start with '$'. - When referring to an anchor in a check use the same numeric variable syntax that FileCheck already supports: `CHECK: [[#ANCHOR_NAME]][[#ANCHOR_NAME+1]]` Here is a brief (contrived) example of the usage of this: ``` #define BAD_FUNCTION() badFunction() // LINE-ANCHOR: BAD_FUNC // Further down in the file BAD_FUNCTION(); CHECK-NOTES: [[@LINE-1]]:3: warning: called a bad function CHECK-NOTES :[[#BAD-FUNC]]:3: note: expanded from macro 'BAD_FUNCTION' ``` Regards, Nathan James

...; number that where they were defined. > > I think something like this could be useful. However, I think it > would be more useful to have a general directive for defining > FileCheck variables inline without trying to capture from input. For > example: > > ``` > #define BAD_FUNCTION() badFunction() // CHECK-DEFINE: > [[#BAD_FUNC:@LINE]] > // Further down in the file > BAD_FUNCTION(); > CHECK-NOTES: [[@LINE-1]]:3: warning: called a bad function > CHECK-NOTES :[[#BAD_FUNC]]:3: note: expanded from macro > 'BAD_FUNCTION' > ``` > > The exact...

For the package at http://www.cs.cas.cz/~savicky/R-devel/something_0.0.0.tar.gz which is a minor part of some other package only to demonstrate the problem, i get (under R version 2.11.0 Under development 2009-12-12 r50714 and also under R-2.9.2, openSUSE 11.1 (x86_64) and CentOS release 5.2) R CMD check something_0.0.0.tar.gz ... * checking Rd files ... OK * checking Rd metadata ...