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 simply returns a list with a) the 
returned value, and b) its visibility:

 > withVisible( a <- c(1, 2, 3, 4, 5, 6) )
$value
[1] 1 2 3 4 5 6

$visible
[1] FALSE

 > withVisible( c(1, 2, 3, 4, 5, 6) )
$value
[1] 1 2 3 4 5 6

$visible
[1] TRUE


something similar might be useful in this case as well?

Carson

-- 
Carson J. Q. Farmer
ISSP Doctoral Fellow
National Centre for Geocomputation (NCG),
Email: carson.far...@gmail.com
Web:   http://www.carsonfarmer.com/
       http://www.ftools.ca/



------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to