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 09:58:09 UTC

List: ruby-core #11494

> > It is because the and サ characters are not in ISO-8859-1.
>
> The characters were in UTF-8, which is why I asked iconv to convert
> them.  Don't take my word for it though, I gave you the source so you
> could double-check me.

Sorry, my mistake, ォ and サ are indeed in ISO 8859-1. It's just that
they were displayed as question mark which is the default character
used by iconv when a characters is not in the destination encoding.
But here it seems it's the terminal that displays it, not iconv.

> > The ? character has the same code in both UTF-8 and ISO-8859-1 as it
> > is an ASCII character...
>
> My text editor and terminal don't agree
> Firefly:~/Desktop$ cat saved_as_utf8.txt saved_as_latin1.txt
> ォサ
> ??
> Firefly:~/Desktop$ ruby -e 'p ARGF.read' saved_as_utf8.txt
> saved_as_latin1.txt
> "\302\253\302\273\n\253\273\n"

In fact nobody is wrong. I was talking about the question mark (?)
character that is indeed an ASCII character and so the has the same
code in both UTF-8 and ISO 8859-1.
The "question mark" you are refering to is not a question mark but an
invalid UTF-8 character that is displayed by the terminal as a
question mark.

> I'd view ォ and サ as the same kind of punctuation as ". So it's not a
> letter. And \b should match at letter <> non-letter boundaries.

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.

Thread

Prev Next

In This Thread

Prev Next