Displaying 5 results from an estimated 5 matches for "environmentns".
Did you mean:
environment's
2016 Oct 03
4
On implementing zero-overhead code reuse
Hi Frederick,
I described what I meant in the post I sent to R-help
(https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html),
but in brief, by "zero overhead" I mean that the only thing needed for
library code to be accessible to client code is for it to be located
in designed directory. No additional meta-files, packaging/compiling,
etc. are required.
Best,
G.
On Sun, Oct
2016 Oct 03
3
On implementing zero-overhead code reuse
On Mon, Oct 3, 2016 at 10:18 AM, <frederik at ofb.net> wrote:
> Hi Kynn,
>
> Thanks for expanding.
>
> I wrote a function like yours when I first started using R. It's
> basically the same up to your "new.env()" line, I don't do anything
> with environmentns. I just called my function "mysource" and it's
> essentially a "source with path". That allows me to find code I reuse
> in standard locations.
>
> I don't know why R does not have built-in support for such a thing.
> You can get it in C compilers with CPA...
2016 Oct 03
0
On implementing zero-overhead code reuse
Hi Kynn,
Thanks for expanding.
I wrote a function like yours when I first started using R. It's
basically the same up to your "new.env()" line, I don't do anything
with environmentns. I just called my function "mysource" and it's
essentially a "source with path". That allows me to find code I reuse
in standard locations.
I don't know why R does not have built-in support for such a thing.
You can get it in C compilers with CPATH, and as you say in Pe...
2016 Oct 03
0
On implementing zero-overhead code reuse
...8 AM, <frederik at ofb.net> wrote:
>>
>> Hi Kynn,
>>
>> Thanks for expanding.
>>
>> I wrote a function like yours when I first started using R. It's
>> basically the same up to your "new.env()" line, I don't do anything
>> with environmentns. I just called my function "mysource" and it's
>> essentially a "source with path". That allows me to find code I reuse
>> in standard locations.
>>
>> I don't know why R does not have built-in support for such a thing.
>> You can get it in...
2016 Oct 03
2
On implementing zero-overhead code reuse
...; wrote:
>>>
>>> Hi Kynn,
>>>
>>> Thanks for expanding.
>>>
>>> I wrote a function like yours when I first started using R. It's
>>> basically the same up to your "new.env()" line, I don't do anything
>>> with environmentns. I just called my function "mysource" and it's
>>> essentially a "source with path". That allows me to find code I reuse
>>> in standard locations.
>>>
>>> I don't know why R does not have built-in support for such a thing.
>>>...