Professor Ripley
You asked “how that managed to give TRUE? (I apologize for the mangled quotes —
the error occurred with plain quotes).
All that I can say is that R versions <= 3.1.0 allowed my code to execute
without error. The bug report appears to address the issue. I typically
review Dalg
On 07/08/2014 23:37, Fisher Dennis wrote:
R 3.1.1
OS X (and Windows)
Colleagues
I have some code that manages files. Previously (as late as 3.1.0), the
command:
file.info(FILENAME)$mtime == “”
yielded T/F
Now, it triggers an error:
Error in as.POSIXlt.character(x, tz, ...) :
Are you aware you have so-called smart quotes in your R code? That can
cause all sorts of interesting errors, though I don't get the exact
one you report.
Sarah
On Thu, Aug 7, 2014 at 6:37 PM, Fisher Dennis wrote:
> R 3.1.1
> OS X (and Windows)
>
> Colleagues
>
> I have some code that manages fi
R 3.1.1
OS X (and Windows)
Colleagues
I have some code that manages files. Previously (as late as 3.1.0), the
command:
file.info(FILENAME)$mtime == “”
yielded T/F
Now, it triggers an error:
Error in as.POSIXlt.character(x, tz, ...) :
character string is not in a stan
4 matches
Mail list logo