Hi Dirk,
Thanks for your response, I get the point on return(). For me, it is a security
blanket - I just need to let that go rather than justify keeping it. I will
refactor the connections and just get comfortable without return().
Thanks,
Glenn
On Aug 10, 2015, at 09:59 PM, Dirk Eddelbuette
On 11 August 2015 at 02:09, Glenn Schultz wrote:
| All,
| Is my function just plain wrong or is it just programming style? I use
connections because SODA (software for data analysis) recommends using
connections when working with serialized files.
Nothing wrong with connections. Many of us u
All,
Is my function just plain wrong or is it just programming style? I use
connections because SODA (software for data analysis) recommends using
connections when working with serialized files.
First, after researching the use of return() - following Joshua's comment and
others I found a p
Thanks Jenny! Just the advice I was looking for.
On Mon, Aug 10, 2015 at 4:40 PM, Jennifer Bryan wrote:
> Hi Jonathan,
>
> Re: this note: no visible binding for global variable ‘datetime’
>
> In programming and packages, it is recommended to use special versions of
> dplyr’s single table verbs,
Hi Jonathan,
Re: this note: no visible binding for global variable ‘datetime’
In programming and packages, it is recommended to use special versions of
dplyr’s single table verbs, e.g., use `filter_()` as opposed to `filter()`.
Note the underscore. The “underscore” functions use standard evalua
On 11.08.2015 00:35, Jonathan Callahan wrote:
Greetings,
I'm using dplyr inside of another package with examples like this:
data <- dplyr::filter(data, datetime >= trange[1], datetime <= trange[2])
When I run my package through R CMD check I get the following NOTES:
monitorSubsetData: no vis
Greetings,
I'm using dplyr inside of another package with examples like this:
data <- dplyr::filter(data, datetime >= trange[1], datetime <= trange[2])
When I run my package through R CMD check I get the following NOTES:
monitorSubsetData: no visible binding for global variable ‘datetime’
I
Dear All,
I have a package that uses reference classes. When I build the package I
get numerous notes of the sort
Note: no visible binding for '<<-' assignment to 'pars'
I've tried using GlobalVariables, but that didn't solve the issue.
After some googling, I came across the page
http://stackov
> On 10 Aug 2015, at 19:47 , Ignacio Martinez wrote:
>
> Thanks peter.
>
> 1. Does it say anywhere that the build process should use src/Makevars?
> I'm not sure, where should it say that? I'm using the default options in
> Rstudio to create a package
It actually is discussed in Writing R Ext
Thanks peter.
1. Does it say anywhere that the build process should use src/Makevars?
I'm not sure, where should it say that? I'm using the default options in
Rstudio to create a package
2. Also notice that an important part of the package concept is that
packages can be distributed.
The package
> On 10 Aug 2015, at 19:25 , Ignacio Martinez wrote:
>
> Hi,
>
> I'm learning to develop R packages that use Fortran (and MPI). I recently
> asked a question on stack-overflow and I was told to contact this list with
> a followup question.
>
> When I add to src/Makevars the follwoing line
>
>
Hi,
I'm learning to develop R packages that use Fortran (and MPI). I recently
asked a question on stack-overflow and I was told to contact this list with
a followup question.
When I add to src/Makevars the follwoing line
FC=mpif90
Rstudio ignores it when I click `Build and Reload`. But, if I c
12 matches
Mail list logo
