ruby-core

So, is it correct to assume that for language constructs that create built-in types like Range, Array, Hash etc that user-defined initialize methods are never called?

[#11549] Re: Proc initialize method not called under certain circumstances — "Berger, Daniel" <Daniel.Berger@...> 2007/06/28

> -----Original Message-----

[#11550] Re: Proc initialize method not called under certain circumstances — MenTaLguY <mental@...> 2007/06/28

On Fri, 29 Jun 2007 06:24:48 +0900, "John Lam (CLR)" <jflam@microsoft.com> wrote:

[#11553] Re: Proc initialize method not called under certain circumstances — "Marcel Molina Jr." <marcel@...> 2007/06/28

On Fri, Jun 29, 2007 at 06:54:49AM +0900, MenTaLguY wrote:

[#11554] Re: Proc initialize method not called under certain circumstances — murphy <murphy@...> 2007/06/28

> ... for language constructs that create

[#11560] Re: Proc initialize method not called under certain circumstances — Yukihiro Matsumoto <matz@...> 2007/06/29

Hi,

[#11548] NilClass, TrueClass, FalseClass special cased for singleton classes? — "John Lam (CLR)" <jflam@...>

If you do:

3 messages 2007/06/28

[#11557] Re: NilClass, TrueClass, FalseClass special cased for singleton classes? — Nobuyoshi Nakada <nobu@...> 2007/06/29

Hi,

[#11559] Re: NilClass, TrueClass, FalseClass special cased for singleton classes? — Joel VanderWerf <vjoel@...> 2007/06/29

John Lam (CLR) wrote:

[#11555] Name of Classes — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>

Moin, moin!

2 messages 2007/06/28

[#11558] Re: Name of Classes — Nobuyoshi Nakada <nobu@...> 2007/06/29

Moin,

[#11556] delete_if with destructive methods in block — Florian Gross <florgro@...>

Hi,

3 messages 2007/06/29

[#11561] Re: [BUG] delete_if with destructive methods in block — Nobuyoshi Nakada <nobu@...> 2007/06/29

Hi,

[#11567] Re: delete_if with destructive methods in block — Florian Gross <florgro@...> 2007/06/30

That fixes it for me. I got no regressions from Rubinius' hash spec

[#11562] Can clear frozen array using initialize() — Florian Gross <florgro@...>

Hi,

2 messages 2007/06/29

[#11563] Re: [BUG] Can clear frozen array using initialize() — Yukihiro Matsumoto <matz@...> 2007/06/30

Hi,

Re: Ruby Changes Its Mind About Non-Word Characters

From: "Vincent Isambart" <vincent.isambart@...>

Date: 2007-06-17 10:22:37 UTC

List: ruby-core #11496

> I agree that the and サ are logically quotes (after all I'm French
> and they are used a lot in French), but what I said is that the
> Unicode support for Ruby 1.8 is poor (in fact except split(//) you
> can't do much) so I am not that suprised by the fact it does not work.

I just checked in ruby 1.8.6's code what was done and it is indeed
quite simple. Everything is based on whether a character "is a letter"
or not, and "is a letter" is defined by (I simplified it a bit):
- if the characters is an ASCII character (ASCII code <= 127) or the
multibyte character mode is ASCII (the default if you did not change
it), the result is what says the standard C function isalnum (is alpha
numeric)
- if the characters code is bigger that 127 and the multibyte
character mode is not ASCII, it "is a letter" if the character takes
more than one byte. And in UTF-8, _all_ characters with a code bigger
than 127 take at least 2 bytes.

So in ruby 1.8 in UTF-8 mode, all non ASCII characters are considered a letter.

Yes it is not a good thing but think that this is not so simple,
knowing if a Unicode character is a letter or not requires a better
regexp engine, including tables with the attributes of all Unicode
characters. But for that you will need to use ruby 1.9. Tim Bray had
reasons to say that Unicode support in ruby 1.8 sucked. And Matz knows
it, that's what ruby 1.9 will be better on this point.

Thread

Prev Next

In This Thread

Prev Next