From romain at r-enthusiasts.com  Fri Dec 13 00:18:54 2013
From: romain at r-enthusiasts.com (=?windows-1252?Q?Romain_Fran=E7ois?=)
Date: Fri, 13 Dec 2013 00:18:54 +0100
Subject: [Rd] internal manipulation of ...
In-Reply-To: <25A6CE5E-D2FC-409D-8AD8-BAE87EAD68C5@r-project.org>
References: <EDC77346-95D8-4562-A49C-889109F5DF92@r-enthusiasts.com>
	<25A6CE5E-D2FC-409D-8AD8-BAE87EAD68C5@r-project.org>
Message-ID: <91773308-D979-42D4-9450-D4BA6518F1DC@r-enthusiasts.com>


Le 13 d?c. 2013 ? 00:15, Simon Urbanek <simon.urbanek at r-project.org> a ?crit :

> 
> On Dec 12, 2013, at 3:32 PM, Romain Fran?ois <romain at r-enthusiasts.com> wrote:
> 
>> Hello, 
>> 
>> I?m looking for examples on how to manipulate the ... internally, e.g. in a .Call or .External function. 
>> 
>> I?m particularly interested in accessing the environment in which each contribution to ... can be evaluated. 
>> 
> 
> Arguments in ... are evaluated *before* being passed down to .Call/.External so there is no ... by the time you enter the C code. AFAIR R doesn't allow you to get at the promises outside of internal code, so you either get the call or the values, but nothing in between.
> 
> Cheers,
> Simon

Thanks. That confirms what I feared. 
Back at low level manipulation of call stack and frame stack then. :/

Romain


[Rd] internal manipulation of ...
=?windows-1252?Q?Romain_Fran=E7ois?=