R help - Mar 2009 - R CMD check detects parse error, but in which file?

Hello

I looked on the archives but did not find answer for that...

Running R CMD check for a package, i get an error:

Error in parse(n = -1, file = file) : unexpected symbol at
3341: }

But how can I find which file is guilty? What is this 3342 referring to?

Finally the solution I found is to source() every file until I find the 
file where the problem is... Is there some better way to do it? With a 
debuger? thanks a lot!

Matthieu Stigler

Matthieu Stigler wrote:
> Hello
> 
> I looked on the archives but did not find answer for that...
> 
> Running R CMD check for a package, i get an error:
> 
> Error in parse(n = -1, file = file) : unexpected symbol at
> 3341: }
> 
> But how can I find which file is guilty? What is this 3342 referring to?

Given I remember correctly without looking into the details:
It is the line number in the concatenated file (of all your .R files, by 
default sorted in a C locale).


> Finally the solution I found is to source() every file until I find the 
Yes, this is probably the quickest way. source() them using a loop that 
reports which one fails.


You may want to try out R-devel which tells you which of your R files is 
the culprit.

Uwe Ligges


> file where the problem is... Is there some better way to do it? With a 
> debuger? thanks a lot!
> 
> Matthieu Stigler
> 
> ______________________________________________
> R-help at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide 
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.

Matthieu Stigler wrote:
> Hello
>
> I looked on the archives but did not find answer for that...
>
> Running R CMD check for a package, i get an error:
>
> Error in parse(n = -1, file = file) : unexpected symbol at
> 3341: }
>
> But how can I find which file is guilty? What is this 3342 referring to?
>
> Finally the solution I found is to source() every file until I find 
> the file where the problem is... Is there some better way to do it? 
> With a debuger? thanks a lot!
>
Hi Matthieu,
My understanding (and I may get clipped up alongside the head if I'm 
wrong) is that R concatenates all the source code into one big file hen 
checking and the number is the line number in that file. The error 
message may mean that you have an extra right parenthesis in that line 
(or very near to).


Jim