Displaying 8 results from an estimated 8 matches for "proj_r_lib".
2016 Oct 02
5
On implementing zero-overhead code reuse
...I've described this idea in more detail, and the motivation for this
question in an earlier post to R-help
(https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
(One of the responses I got advised that I post my question here instead.)
The best I have so far is to configure my PROJ_R_LIB environment
variable to point to the directory with my shared code, and put a
function like the following in my .Rprofile file:
import <- function(name){
## usage:
## import("foo")
## foo$bar()
path <- file.path(Sys.getenv("PROJ_R_LIB")...
2016 Oct 03
4
On implementing zero-overhead code reuse
...he motivation for this
>> question in an earlier post to R-help
>> (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
>>
>> (One of the responses I got advised that I post my question here instead.)
>>
>> The best I have so far is to configure my PROJ_R_LIB environment
>> variable to point to the directory with my shared code, and put a
>> function like the following in my .Rprofile file:
>>
>> import <- function(name){
>> ## usage:
>> ## import("foo")
>> ## foo$bar()
&...
2016 Oct 02
0
On implementing zero-overhead code reuse
...in more detail, and the motivation for this
> question in an earlier post to R-help
> (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
>
> (One of the responses I got advised that I post my question here instead.)
>
> The best I have so far is to configure my PROJ_R_LIB environment
> variable to point to the directory with my shared code, and put a
> function like the following in my .Rprofile file:
>
> import <- function(name){
> ## usage:
> ## import("foo")
> ## foo$bar()
> path <- file...
2016 Oct 04
0
On implementing zero-overhead code reuse
...ea in more detail, and the motivation for this
> question in an earlier post to R-help
> (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
>
> (One of the responses I got advised that I post my question here instead.)
>
> The best I have so far is to configure my PROJ_R_LIB environment
> variable to point to the directory with my shared code, and put a
> function like the following in my .Rprofile file:
>
> import <- function(name){
> ## usage:
> ## import("foo")
> ## foo$bar()
> path <- file....
2016 Oct 03
3
On implementing zero-overhead code reuse
...post to R-help
> > >> (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
> > >>
> > >> (One of the responses I got advised that I post my question here
> instead.)
> > >>
> > >> The best I have so far is to configure my PROJ_R_LIB environment
> > >> variable to point to the directory with my shared code, and put a
> > >> function like the following in my .Rprofile file:
> > >>
> > >> import <- function(name){
> > >> ## usage:
> > >>...
2016 Oct 03
0
On implementing zero-overhead code reuse
...t;> question in an earlier post to R-help
> >> (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
> >>
> >> (One of the responses I got advised that I post my question here instead.)
> >>
> >> The best I have so far is to configure my PROJ_R_LIB environment
> >> variable to point to the directory with my shared code, and put a
> >> function like the following in my .Rprofile file:
> >>
> >> import <- function(name){
> >> ## usage:
> >> ## import("foo")
&...
2016 Oct 03
0
On implementing zero-overhead code reuse
...(https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html).
>> > >>
>> > >> (One of the responses I got advised that I post my question here
>> > >> instead.)
>> > >>
>> > >> The best I have so far is to configure my PROJ_R_LIB environment
>> > >> variable to point to the directory with my shared code, and put a
>> > >> function like the following in my .Rprofile file:
>> > >>
>> > >> import <- function(name){
>> > >> ## usage:
>&...
2016 Oct 03
2
On implementing zero-overhead code reuse
...tat.ethz.ch/pipermail/r-help/2016-September/442174.html).
>>>>>>
>>>>>> (One of the responses I got advised that I post my question here
>>>>>> instead.)
>>>>>>
>>>>>> The best I have so far is to configure my PROJ_R_LIB environment
>>>>>> variable to point to the directory with my shared code, and put a
>>>>>> function like the following in my .Rprofile file:
>>>>>>
>>>>>> import <- function(name){
>>>>>> ## us...