[#9722] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters — <noreply@...>

Bugs item #7278, was opened at 2006-12-14 13:59

8 messages 2006/12/14

[#9749] System V IPC in standard library? — Steven Jenkins <steven.jenkins@...>

Back in August, I needed a semaphore to serialize access to an external

14 messages 2006/12/19

[#9753] CVS freeze — SASADA Koichi <ko1@...>

Hi,

20 messages 2006/12/20
[#9755] Re: [ruby-dev:30039] CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

[#9757] Re: [ruby-dev:30040] Re: CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

Re: [ ruby-Bugs-6820 ] #ancestors never includes the singleton class (inconsistent)

From: "Wilson Bilkovich" <wilsonb@...>
Date: 2006-12-19 17:09:19 UTC
List: ruby-core #9747
On 12/18/06, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
> Hi,
>
> In message "Re: [ ruby-Bugs-6820 ] #ancestors never includes the singleton class (inconsistent)"
>     on Thu, 30 Nov 2006 21:55:33 +0900, dblack@wobblini.net writes:
>
> |I tend to agree.  Anonymous classes are visible in ancestors, and
> |singleton classes are anonymous classes.  They are special in the
> |sense that they can't be instantiated, but I don't see why they should
> |be treated as special when reflecting on ancestry.
>
> I just remembered I made decision that singleton classes (or
> eigenclasses) were "real" anonymous classes rather than theoretical
> place holder.  That means having singleton classes in ancestors list
> makes sense.  I will change the behavior in the future.
>
> This is a step toward eigenclass method.
>

Is this an implicit vote for the 'eigenclass' name, or just a useful
placeholder?
I ask because Rubinius is currently calling this 'metaclass', and it
would be nice to keep the terminology in sync.
By 'in sync', I mean that we would change to match the official name. Heh.

Regards,
--Wilson.

In This Thread