Where do things stand with respect to the 1-byte trace instruction and
a trace instruction-replacement mechanism? There was some discussion a
while back as to whether or not this was going to get into 1.9.1.

Thanks.

On Tue, Sep 2, 2008 at 2:09 AM, Yugui (Yuki Sonoda) <yugui / yugui.jp> wrote:
> Hi all,
>
> As announced before, Ruby 1.9.1 features will be frozen on 25 September.
>
> After the time,
>  * Ruby level APIs must not changed.
>  * C level APIs will must not changed without discussion on
> ruby-core/ruby-dev.
>   * All structures, data types, variables, functions and macros in
> include/ruby/*.h are regarded as public C level APIs.
>   * Move it from include/ruby/*.h anything you want not to publish.
>
> And I will create the ruby_1_9_1 branch and release 1.9.1 RC1 on 25
> October. After the time,
>  * C level APIs will must not changed.
>
> Also the C level APIs of 1.9.x must have backward binary-compatibility
> to 1.9.1.
>
>
> Regards,
>
> -- Yuki Sonoda (Yugui) <yugui / yugui.jp>
>
>