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: Patching win32 ruby fopen/opendir/stat/rename/unlink to work with UTF8 paths?

From: Daniel Berger <djberg96@...>

Date: 2007-06-07 01:05:13 UTC

List: ruby-core #11423

Bill Kelly wrote:
> Hi,
> 
> I'm using ruby in a Unicode-aware cross-platform application.
> We use UTF8, and on OS X unicode paths and filenames "just work",
> because the underlying fopen(), etc. calls understand UTF8.
> 
> Of course, things are not so nice on Windows.
> 
> I'm considering patching the stdlib calls used by ruby to use
> UTF8 behind-the-scenes on Windows.
> 
> Either by #define fopen(name, mode) utf8_fopen(name, mode)
> 
> Or by just changing ruby's use of fopen to utf8_fopen.  (And
> then make utf8_fopen simply defined back to fopen on non-
> Windows systems.)

You can look here for how to implement it in Windows. I have no idea 
what platforms support utf8_fopen and which don't.

http://www.koders.com/c/fid7D9DF187D3F371F71F7D6B1779A4EF93316425B9.aspx

> What I'm wondering is,
> 
> 1. Has anyone already tried this?  It seems to be it should
> be pretty straightforward.  Can anyone think of a reason why it might 
> not be easy?

Cross platform issues will be the number 1 issue I imagine. But, it's 
certainly possible.

> 2. Would anyone here be interested in such a patch?  I'm asking
> because I'd like to make the changes in the most harmonious way
> possible.  For example, would the #define fopen approach above be
> preferred?  Or changing fopen to utf8_fopen?

I vote that you write it and submit it. It may or may not be accepted, 
but you can at least try. :)

Regards,

Dan

Thread

Prev Next

In This Thread

Prev Next