From: Eric Wong <normalperson@...>
Date: 2013-09-24T21:00:44+00:00
Subject: [ruby-core:57356] Re: [ruby-trunk - Bug #8399] Remove usage of RARRAY_PTR in C extensions when not needed

SASADA Koichi <ko1@atdot.net> wrote:
> (2013/05/15 14:38), dbussink (Dirkjan Bussink) wrote:
> > If we're changing something anyway, it makes far more sense to change to either RARRAY_AREF or rb_ary_entry in extensions. I also discussed this on irc (#ruby-core) with ko1 and he also agrees with me in that respect. 
> 
> My thoughts are:
> 
>   (1) rb_ary_entry() (and accessor APIs) is enough for most of case
>       (except perforamance such as Hanmac said [ruby-core:55003])
>       So I agree with dbussink that recooment such APIs for C ext
>       programmer is good idea. For example, emphasize in README.ext.

Hi, it looks like the API is mostly fleshed out now since 2.1.0preview1
is released.

Can you please update README.EXT with advice for using (or avoiding)
RARRAY_* family of macros?  I haven't been able to take the time
to fully-understand the new ones.

Thank you.