This is why I only put localization variables in .Rprofile and am always
putting such options into my project-specific scripts.
This may sound like I am a masochist, but I hate sharing my scripts with
someone else contaminated with compatibility bombs like that.
On July 6, 2019 8:19:27 PM PDT,
Just thought it might be of interest were I to give a progress report
( :-) ) on this problem.
I managed to track down and fix what was going wrong. It turns out that
the issue was "stringsAsFactors". I *hate* stringsAsFactors being TRUE
so I have a call to options() setting it to FALSE in
Dear List,
I have been informed that the most recent upload of our swephR package
triggers stack-buffer-overflow. See for example
https://www.stats.ox.ac.uk/pub/bdr/memtests/clang-ASAN/swephR. The
reason seems to be quite obvious (an array has been declared with 36
instead of 37 elements), but I w
Thanks. This is exactly what I needed.
Thanks
-Alex
On Sat, Jul 6, 2019 at 10:10 AM Dirk Eddelbuettel wrote:
>
> On 6 July 2019 at 09:27, Alex Hallam wrote:
> | I have been working on making a data package. The goal is to one day push
> | it to CRAN, but I am having 2 problems (one warning and
On 6 July 2019 at 09:27, Alex Hallam wrote:
| I have been working on making a data package. The goal is to one day push
| it to CRAN, but I am having 2 problems (one warning and one note) from R
| CMD. I think the problems are due to having large files (a 453M csv.7z raw
| file and a 75M .rda fil
I have been working on making a data package. The goal is to one day push
it to CRAN,
but I am having 2 problems (one warning and one note) from R CMD. I think
the problems
are due to having large files (a 453M csv.7z raw file and a 75M .rda file)
Below is my R CMD check.
── R CMD check results ─
