[#11073] segfault printing instruction sequence for iterator — <noreply@...>

Bugs item #10527, was opened at 2007-05-02 14:42

14 messages 2007/05/02
[#11142] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Nobuyoshi Nakada <nobu@...> 2007/05/10

Hi,

[#11188] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Paul Brannan <pbrannan@...> 2007/05/16

On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:

[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>

Hi all.

17 messages 2007/05/25

Re: pattern for implementation-private constants?

From: murphy <murphy@...>
Date: 2007-05-08 01:43:23 UTC
List: ruby-core #11110
> It seems to me that class implementations often benefit from the
> use of constants
constants aren't the fastest variable type currently. however, YARV did
a good job, and now they are. my benchmarks yield:

# Ruby 1.8.6:
# global variable       0.490 ===============
# local variable        0.495 ===============
# constant              0.570 =================
# instance variable     0.573 =================
# class variable        0.612 ==================
# method                1.224 =====================================

# Ruby 1.9.0 (2007-04-24)
# constant              0.305 =========
# local variable        0.306 =========
# global variable       0.326 ==========
# instance variable     0.441 =============
# class variable        0.475 ==============
# method                0.626 ===================

> The only one I can think of is to define methods whose names begin with
> capital letters and therefore look like constants.
cool idea, but Ruby may force you to use Foo() then.

[murphy]


In This Thread