Both the following lines return 0 hits
grep printf *.c|grep -v Rprintf|grep -v fprintf
grep puts *.c
Is there some way to detect what has caused this warning about puts?
It's not a call to 'puts' or 'printf' because there are none.
Longshot:
grep '[^Rf]printf' *.c
Peter's longshot hit the
Following Simon's suggestion of replacing printf with Rprintf throughout
the source code R CMD check now complains less than before, but it still
complains...
I used the following two BASH lines to replace printf
find . -maxdepth 1 -type f -name '*.c' -exec sed -i 's\printf\Rprintf\'
{} \;
Many thanks for these comments Simon, that really helps me a lot!
warm regards
David
On 23/04/13 19:30, Simon Urbanek wrote:
On Apr 23, 2013, at 12:43 PM, dpleydell wrote:
Many thanks Simon for your response
Identifying the source of the message is a non-trivial problem because
I've been developing a package called foobar for a couple of years now.
It has evolved through various versions, but has always contained
compiled C code. Recently, R CMD check has started generating the
following message
[START QUOTE]
R CMD check foobar_1.7.5.tar.gz
* using log directory
Many thanks Simon for your response
Identifying the source of the message is a non-trivial problem because there
are a large number of calls to printf and fprintf etc in several thousands
of lines of code spread over many different *.c files.
There should be none, so apparently you have
