Nathaniel Smith wrote:
> On Tue, Mar 3, 2009 at 4:12 AM, Laurent Gautier wrote:
>> but my concern is over possible object duplication when returning from
>> 'function(*args, **kwargs)' (not necessarily the case, but if something is
>> invisible and I can't get rid of copying this is annoying - I n
On Tue, Mar 3, 2009 at 4:12 AM, Laurent Gautier wrote:
> but my concern is over possible object duplication when returning from
> 'function(*args, **kwargs)' (not necessarily the case, but if something is
> invisible and I can't get rid of copying this is annoying - I need more
> thinking about th
Carson Farmer wrote:
> Laurent (et al.),
>> Right now having R_Visible as a global is ok for 2.0.x, but for 2.1.x
>> I will be considering whether a call to an invisibly returning
>> function should return None to Python, or else (visibility attribute
>> with the returned objects, etc...).
> The
Laurent (et al.),
> Right now having R_Visible as a global is ok for 2.0.x, but for 2.1.x
> I will be considering whether a call to an invisibly returning
> function should return None to Python, or else (visibility attribute
> with the returned objects, etc...).
The output of withVisible in R s
