Peter wrote:
> On Thu, Nov 20, 2008 at 12:02 AM, Nathaniel Smith <[EMAIL PROTECTED]> wrote:
>   
>> In particular, looking at Rinternals.h, VECTOR_ELT etc. are defined in
>> terms of calculating direct memory offsets from an SEXPREC.  Not only
>> are there no strides (necessary for column-major R to grok row-major
>> Numpy arrays), but you can't even have a SEXPREC that points to an
>> array stored elsewhere in memory -- if you want a vector to be visible
>> in R space, you have to stick a header struct right on the front of
>> it.
>>
>>     
>
> I believe NumPy can use row-wise or column-wise (Fortran style)
> arrays.  Perhaps any numpy arrays using the Fortran convention could
> be passed to/from R more efficiently?
>
> Peter
>   
Uh, uh... there might be an oversight about that in rpy2.rinterface 
(column-wise is assumed).

(I am not using numpy very often those days - I remember thinking of 
that I should pay attention to that... but it eventually drifted off the 
radar. Now I see that there are missing unit tests)



L.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to