ruby-core

Mailing Lists

ruby-list (For Ruby users, JA) ruby-dev (For Ruby developers, JA) ruby-core (For Ruby developers, EN) ruby-talk (For Ruby users, EN)
2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002
1 2 3 4 5 6 7 8 9 10 11 12

[#7806] Ruby fails to parse valid wsdl — noreply@...

Bugs item #4336, was opened at 2006-05-02 12:55

1 message 2006/05/02

[#7807] Ruby fails float 80 test in stable tarball (2 May 2006) when compiled with Mingw — noreply@...

Bugs item #4339, was opened at 2006-05-02 19:56

2 messages 2006/05/02
[#7817] Re: [ ruby-Bugs-4339 ] Ruby fails float 80 test in stable tarball (2 May 2006) when compiled with Mingw — Yukihiro Matsumoto <matz@...> 2006/05/03

Hi,

[#7808] one bug and one false positive defect in yaml2byte.c (we think) — "Pat Eyler" <rubypate@...>

We've been looking at coverity defects during our hacking night. there are two

1 message 2006/05/03

[#7809] uninit bug in yaml/emitter.c — "Pat Eyler" <rubypate@...>

During our hacking night, we also looked at an UNINIT bug in yaml/emitter.c

4 messages 2006/05/03
[#7816] Re: uninit bug in yaml/emitter.c — Yukihiro Matsumoto <matz@...> 2006/05/03

Hi,
[#7826] Re: uninit bug in yaml/emitter.c — why the lucky stiff <ruby-core@...> 2006/05/05

Yukihiro Matsumoto wrote:
[#7830] Re: uninit bug in yaml/emitter.c — Joel VanderWerf <vjoel@...> 2006/05/05

why the lucky stiff wrote:

[#7810] patch for UNINIT error in array.c — "Pat Eyler" <rubypate@...>

Along with the unitialized beg, we found a len which doesn't appear to be

1 message 2006/05/03

[#7811] Sather-like iterators — noreply@...

Bugs item #4341, was opened at 2006-05-03 05:28

1 message 2006/05/03

[#7812] Re: patch for UNINIT error in array.c — "Brown, Warren" <warrenbrown@...>

> Along with the unitialized beg, we found a len which

1 message 2006/05/03

[#7813] :!~ not a symbol — noreply@...

Bugs item #4344, was opened at 2006-05-03 17:41

4 messages 2006/05/03
[#7815] Re: [ ruby-Bugs-4344 ] :!~ not a symbol — Yukihiro Matsumoto <matz@...> 2006/05/03

Hi,
[#7827] Re: [ ruby-Bugs-4344 ] :!~ not a symbol — why the lucky stiff <ruby-core@...> 2006/05/05

Yukihiro Matsumoto wrote:
[#7828] Re: [ ruby-Bugs-4344 ] :!~ not a symbol — Yukihiro Matsumoto <matz@...> 2006/05/05

[#7814] parsedate doesn't work with GMT dates — noreply@...

Bugs item #4345, was opened at 2006-05-03 08:26

1 message 2006/05/03

[#7818] (security-related) patch to ALLOC macros to prevent integer overflow bugs — "Dominique Brezinski" <dominique.brezinski@...>

While fixing the integer overflow in rb_ary_fill(), it occurred to me

4 messages 2006/05/04
[#7819] Re: (security-related) patch to ALLOC macros to prevent integer overflow bugs — Hugh Sasse <hgs@...> 2006/05/04

On Thu, 4 May 2006, Dominique Brezinski wrote:
[#7820] Re: (security-related) patch to ALLOC macros to prevent integer overflow bugs — Yukihiro Matsumoto <matz@...> 2006/05/04

Hi,
[#7821] Re: (security-related) patch to ALLOC macros to prevent integer overflow bugs — "Dominique Brezinski" <dominique.brezinski@...> 2006/05/04

On 5/4/06, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:

[#7822] StringScanner#scan() fails on zero-length matches at eos — noreply@...

Bugs item #4361, was opened at 2006-05-04 21:52

1 message 2006/05/04

[#7823] Coverity: Patch/Fix CID 17 OVERRUN_STATIC File: ruby/signal.c — Kevin Tew <tewk@...>

This is a simple out of bounds array access error.

2 messages 2006/05/05
[#7825] Re: Coverity: Patch/Fix CID 17 OVERRUN_STATIC File: ruby/signal.c — Yukihiro Matsumoto <matz@...> 2006/05/05

Hi,

[#7824] Re: Coverity: Patch/Fix CID 17 OVERRUN_STATIC File: ruby/signal.c — ville.mattila@...

1 message 2006/05/05

[#7829] Ruby fails float 80 test in stable tarball (4 May 2006), on multiple platforms — noreply@...

Bugs item #4365, was opened at 2006-05-05 18:51

1 message 2006/05/05

[#7831] Resolv::DNS and IPv6 nameservers — Stephan Maka <stephan@...>

Hello folks,

3 messages 2006/05/06
[#7836] Re: Resolv::DNS and IPv6 nameservers — Tanaka Akira <akr@...17n.org> 2006/05/06

In article <20060506025652.GA64784@hooker.sin>,
[#7838] Re: Resolv::DNS and IPv6 nameservers — Stephan Maka <stephan@...> 2006/05/06

Tanaka Akira wrote:

[#7832] Re: [python_tutor] Welcome to our (ruby-core ML) You are added automatically — "Coimbra R. Fernando" <fcoimbra@...>

help

1 message 2006/05/06

[#7833] segfault on Proc#call after setting a trace_func — Mauricio Fernandez <mfp@...>

$ cat bug2.rb

6 messages 2006/05/06
[#7834] Re: [BUG] segfault on Proc#call after setting a trace_func — ts <decoux@...> 2006/05/06

>>>>> "M" == Mauricio Fernandez <mfp@acm.org> writes:
[#7835] Re: [BUG] segfault on Proc#call after setting a trace_func — Yukihiro Matsumoto <matz@...> 2006/05/06

Hi,
[#7911] Re: [BUG] segfault on Proc#call after setting a trace_func — nobu@... 2006/05/19

Hi,
[#7912] Re: [BUG] segfault on Proc#call after setting a trace_func — Yukihiro Matsumoto <matz@...> 2006/05/20

Hi,
[#7927] Re: [BUG] segfault on Proc#call after setting a trace_func — nobu@... 2006/05/27

Hi,

[#7837] Coverity CID 14 15 Patch — Kevin Tew <tewk@...>

Both errors stem from the possibility of returning a -1, which signals

1 message 2006/05/06

[#7839] Coverity CID 6 7 Appear to be false positives. — Kevin Tew <tewk@...>

CID 6 appears to be a false positive due to the sequence of assignments

1 message 2006/05/07

[#7840] Re: Coverity CID 14 15 Patch — ville.mattila@...

1 message 2006/05/07

[#7841] Re: Coverity CID 6 7 Appear to be false positives. — ville.mattila@...

1 message 2006/05/07

[#7842] XMLRPC support extended iso8601 DateTime Format — noreply@...

Bugs item #4382, was opened at 2006-05-07 21:51

1 message 2006/05/07

[#7843] Possible YAMl bug in 1.8.4 — Damphyr <damphyr@...>

OK, while parsing the td2 data from the ruby-lang website we stumbled on

10 messages 2006/05/08
[#7846] Re: Possible YAMl bug in 1.8.4 — "Curt Hibbs" <ml.chibbs@...> 2006/05/09

Its probably a bug. I'm not familiar with the specifics, but Ruby
[#7852] Re: Possible YAMl bug in 1.8.4 — MenTaLguY <mental@...> 2006/05/09

On Tue, 9 May 2006 10:51:54 +0900, "Curt Hibbs" <ml.chibbs@gmail.com> wrote:
[#7853] Re: Possible YAMl bug in 1.8.4 — "Curt Hibbs" <ml.chibbs@...> 2006/05/09

You can download it from here:
[#7854] Re: Possible YAMl bug in 1.8.4 — MenTaLguY <mental@...> 2006/05/09

On Wed, 10 May 2006 02:56:09 +0900, "Curt Hibbs" <ml.chibbs@gmail.com> wrote:
[#7849] Re: Possible YAMl bug in 1.8.4 — damphyr@... 2006/05/09

[#7850] Re: Possible YAMl bug in 1.8.4 — James Edward Gray II <james@...> 2006/05/09

On May 9, 2006, at 7:20 AM, damphyr@freemail.gr wrote:
[#7855] Re: Possible YAMl bug in 1.8.4 — Mauricio Fernandez <mfp@...> 2006/05/09

On Tue, May 09, 2006 at 10:51:54AM +0900, Curt Hibbs wrote:
[#7857] Re: Possible YAMl bug in 1.8.4 — "Curt Hibbs" <ml.chibbs@...> 2006/05/09

On 5/9/06, Mauricio Fernandez <mfp@acm.org> wrote:
[#7861] Confirmed: YAML bug in 1.8.4 — why the lucky stiff <ruby-core@...> 2006/05/10

Mauricio Fernandez wrote:

[#7844] buggy tr_s in jcode — noreply@...

Bugs item #4391, was opened at 2006-05-08 22:34

2 messages 2006/05/08
[#7848] Re: [ ruby-Bugs-4391 ] buggy tr_s in jcode — Yukihiro Matsumoto <matz@...> 2006/05/09

Hi,

[#7845] Method call syntax — mathew <meta@...>

Just noticed someone had written this on wikipedia:

4 messages 2006/05/08
[#7847] Re: Method call syntax — Yukihiro Matsumoto <matz@...> 2006/05/09

Hi,
[#7851] Re: Method call syntax — James Edward Gray II <james@...> 2006/05/09

On May 9, 2006, at 12:10 AM, Yukihiro Matsumoto wrote:
[#7856] Re: Method call syntax — Bertram Scharpf <lists@...> 2006/05/09

Hi,

[#7858] Ruby threads working with native threads — "Francis Cianfrocca" <garbagecat10@...>

I recently wrote a network-event extension for Ruby ("eventmachine" in

3 messages 2006/05/10
[#7859] Re: Ruby threads working with native threads — Eric Hodel <drbrain@...7.net> 2006/05/10

On May 10, 2006, at 9:43 AM, Francis Cianfrocca wrote:
[#7860] Re: Ruby threads working with native threads — "Francis Cianfrocca" <garbagecat10@...> 2006/05/10

Thanks, I'll look into that. What I wanted to do was call select(2) on a

[#7862] 650M process, huge stack trace — "Evan Phoenix" <evan@...>

I've been banging my head against the wall trying to figure out why

3 messages 2006/05/11
[#7863] Re: 650M process, huge stack trace — "Timothy J. Wood" <tjw@...> 2006/05/11

[#7864] Re: 650M process, huge stack trace — "Evan Phoenix" <evan@...> 2006/05/11

It's on linux 2.6. A modified debian box.

[#7865] Strange interactions between Struct and 'pp' — noreply@...

Bugs item #4457, was opened at 2006-05-12 17:13

5 messages 2006/05/12
[#7869] Re: [ ruby-Bugs-4457 ] Strange interactions between Struct and 'pp' — Tanaka Akira <akr@...17n.org> 2006/05/13

In article <200605121513.k4CFDWsl029144@rubyforge.org>,
[#7907] Re: [ ruby-Bugs-4457 ] Strange interactions between Struct and 'pp' — Tom Copeland <tom@...> 2006/05/18

On Sat, 2006-05-13 at 16:39 +0900, Tanaka Akira wrote:
[#7866] Re: [ ruby-Bugs-4457 ] Strange interactions between Struct and 'pp' — Eric Hodel <drbrain@...7.net> 2006/05/12

[#7871] Re: [ ruby-Bugs-4457 ] Strange interactions between Struct and 'pp' — Florian Gro<florgro@...> 2006/05/13

Eric Hodel wrote:

[#7867] performance enhancement for OpenSSL::Cipher::Cipher.update — noreply@...

Patches item #4463, was opened at 2006-05-13 06:55

1 message 2006/05/13

[#7868] Better error messages in OpenSSL::SSL.[accept, connect] — noreply@...

Patches item #4464, was opened at 2006-05-13 06:58

1 message 2006/05/13

[#7870] RDoc looks for doc headers at function prototypes — noreply@...

Bugs item #4467, was opened at 2006-05-13 13:50

1 message 2006/05/13

[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>

All, I needed a nonblocking socket connect for my asynchronous-event

18 messages 2006/05/14
[#7873] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/14

In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,
[#7874] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about introducing the method Socket#set_nonblocking, or alternatively
[#7875] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,
[#7876] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

Well, it's ok then. I'm comfortable adding in the nonblocking
[#7877] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/15

Hi,
[#7880] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

How about Socket#nbconnect and Socket#nbaccept?
[#7890] Re: Nonblocking socket-connect — "Vlad GALU" <vladgalu@...> 2006/05/17

On 5/15/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
[#7893] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/17

My opinion only, but when I see bang at the end of a method name, it makes
[#7894] Re: Nonblocking socket-connect — "Austin Ziegler" <halostatue@...> 2006/05/17

On 5/17/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
[#7898] Re: Nonblocking socket-connect — Eric Hodel <drbrain@...7.net> 2006/05/17

On May 17, 2006, at 4:13 AM, Vlad GALU wrote:
[#7900] Re: Nonblocking socket-connect — ara.t.howard@... 2006/05/17

On Thu, 18 May 2006, Eric Hodel wrote:
[#7913] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/20

In article <1147709691.180288.28647.nullmailer@x31.priv.netlab.jp>,
[#7914] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/21

Hi,
[#7915] Re: Nonblocking socket-connect — Sam Roberts <sroberts@...> 2006/05/21

Quoting matz@ruby-lang.org, on Sun, May 21, 2006 at 11:39:21PM +0900:
[#7916] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/21

I also prefer *_nonblock.
[#7917] Re: Nonblocking socket-connect — Tanaka Akira <akr@...17n.org> 2006/05/22

In article <1148222367.676789.19888.nullmailer@x31.priv.netlab.jp>,
[#7918] Re: Nonblocking socket-connect — Yukihiro Matsumoto <matz@...> 2006/05/22

Hi,

[#7878] Re: Nonblocking socket-connect — "Berger, Daniel" <Daniel.Berger@...>

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

2 messages 2006/05/15
[#7879] Re: Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...> 2006/05/15

I have to admit, I seriously dislike AIO. In my experience, it only

[#7881] Segfault on x86_64 when built with -O0 in CFLAGS — noreply@...

Bugs item #4491, was opened at 2006-05-16 12:46

5 messages 2006/05/16
[#7886] Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS — ts <decoux@...> 2006/05/17

>>>>> "n" == noreply <noreply@rubyforge.org> writes:
[#7887] Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS — Yukihiro Matsumoto <matz@...> 2006/05/17

Hi,
[#7888] Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS — Yukihiro Matsumoto <matz@...> 2006/05/17

Hi,
[#7889] Re: [ ruby-Bugs-4491 ] Segfault on x86_64 when built with -O0 in CFLAGS — ts <decoux@...> 2006/05/17

>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:

[#7882] reproducible bug in DRb on OSX — cremes.devlist@...

I've been tearing my hair out the last few days trying to track down

5 messages 2006/05/16
[#7883] Re: reproducible bug in DRb on OSX — Eric Hodel <drbrain@...7.net> 2006/05/16

On May 16, 2006, at 12:25 PM, cremes.devlist@mac.com wrote:
[#7884] Re: reproducible bug in DRb on OSX — cremes.devlist@... 2006/05/17

[#7885] Re: reproducible bug in DRb on OSX — Eric Hodel <drbrain@...7.net> 2006/05/17

On May 16, 2006, at 7:51 PM, cremes.devlist@mac.com wrote:
[#7897] Re: reproducible bug in DRb on OSX — Sam Roberts <sroberts@...> 2006/05/17

Quoting drbrain@segment7.net, on Wed, May 17, 2006 at 12:51:00PM +0900:

[#7891] raise can create custom exception objects which aren't properly initialized — noreply@...

Bugs item #4498, was opened at 2006-05-17 11:36

2 messages 2006/05/17
[#7892] Re: [ ruby-Bugs-4498 ] raise can create custom exception objects which aren't properly initialized — ts <decoux@...> 2006/05/17

>>>>> "n" == noreply <noreply@rubyforge.org> writes:

[#7895] Webrick: Missing -c parameter forces utf-8 even if with code page specified in meta tag — noreply@...

Bugs item #4500, was opened at 2006-05-17 16:44

2 messages 2006/05/17
[#7899] Re: [ ruby-Bugs-4500 ] Webrick: Missing -c parameter forces utf-8 even if with code page specified in meta tag — Eric Hodel <drbrain@...7.net> 2006/05/17

On May 17, 2006, at 7:44 AM, noreply@rubyforge.org wrote:

[#7896] Fwd: Bug: Time#-(1e-6) doesn't substract one microsecond. — Dave Burt <dave@...>

Hi,

1 message 2006/05/17

[#7901] String#nstrip ? — "Daniel Berger" <Daniel.Berger@...>

Hi all,

3 messages 2006/05/18
[#7903] Re: String#nstrip ? — Joel VanderWerf <vjoel@...> 2006/05/18

Daniel Berger wrote:
[#7904] Re: String#nstrip ? — ara.t.howard@... 2006/05/18

On Fri, 19 May 2006, Daniel Berger wrote:

[#7902] Re: String#nstrip ? — "Berger, Daniel" <Daniel.Berger@...>

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

1 message 2006/05/18

[#7905] Re: String#nstrip ? — "Berger, Daniel" <Daniel.Berger@...>

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

3 messages 2006/05/18
[#7906] Re: String#nstrip ? — brabuhr@... 2006/05/18

> > When using the Win32API package, I often have to resort to this idiom
[#7908] Re: String#nstrip ? — Carlos <angus@...> 2006/05/19

Getting STRING[0..(STRING.index(0.chr) || 0)-1]:

[#7909] SCRIPT_LINES__ issue when loading a file more than once — Mauricio Fernandez <mfp@...>

SCRIPT_LINES__ is an obscure feature very few people care about, but I happen

9 messages 2006/05/19
[#7947] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — Mauricio Fernandez <mfp@...> 2006/06/05

On Fri, May 19, 2006 at 06:46:05PM +0900, Mauricio Fernandez wrote:
[#7950] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — Yukihiro Matsumoto <matz@...> 2006/06/05

Hi,
[#7951] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — Mauricio Fernandez <mfp@...> 2006/06/05

On Tue, Jun 06, 2006 at 07:45:52AM +0900, Yukihiro Matsumoto wrote:
[#7952] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — nobu@... 2006/06/06

Hi,
[#7953] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — Yukihiro Matsumoto <matz@...> 2006/06/06

Hi,
[#7956] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — nobu@... 2006/06/06

Hi,
[#7957] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — Yukihiro Matsumoto <matz@...> 2006/06/06

Hi,
[#7958] Re: [PATCH] SCRIPT_LINES__ issue when loading a file more than once — nobu@... 2006/06/06

Hi,

[#7910] Re: String#nstrip ? — "Berger, Daniel" <Daniel.Berger@...>

1 message 2006/05/19

[#7919] Queue — "Francis Cianfrocca" <garbagecat10@...>

Any plans to provide Queue#unshift? Any reason not to?

1 message 2006/05/23

[#7920] Range "max" method does not handle Infinity — noreply@...

Bugs item #4555, was opened at 2006-05-24 04:37

3 messages 2006/05/24
[#7921] Re: [ ruby-Bugs-4555 ] Range "max" method does not handle Infinity — Yukihiro Matsumoto <matz@...> 2006/05/24

Hi,
[#7924] Re: [ ruby-Bugs-4555 ] Range "max" method does not handle Infinity — "C Erler" <erlercw@...> 2006/05/27

On 24/05/06, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:

[#7922] loading rubygems at startup without RUBYOPT — "Nobuyoshi Nakada" <nobu@...>

Hi,

2 messages 2006/05/26
[#8055] Re: loading rubygems at startup without RUBYOPT — nobu@... 2006/06/25

Hi,

[#7923] Nonblocking accept — "Francis Cianfrocca" <garbagecat10@...>

Thanks to the Matz and colleagues for adding the *_nonblock functions. They

3 messages 2006/05/26
[#7925] Re: Nonblocking accept — Tanaka Akira <akr@...17n.org> 2006/05/27

In article <3a94cf510605260529x658e20e1q7d9754266675c3d5@mail.gmail.com>,
[#7926] Re: Nonblocking accept — "Francis Cianfrocca" <garbagecat10@...> 2006/05/27

Thanks for the patch, I'll test as soon as I can. In regard to datagrams,

[#7928] set_trace_func: binding has wrong self value for return events — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...>

Moin.

6 messages 2006/05/27
[#7963] Re: [Bug?] set_trace_func: binding has wrong self value for return events — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2006/06/06

Florian Growrote:
[#7964] Re: [Bug?] set_trace_func: binding has wrong self value for return events — Yukihiro Matsumoto <matz@...> 2006/06/07

Hi,
[#7968] Re: [Bug?] set_trace_func: binding has wrong self value for return events — Florian Gross <florgro@...> 2006/06/07

Yukihiro Matsumoto wrote:
[#7969] Re: [Bug?] set_trace_func: binding has wrong self value for return events — Yukihiro Matsumoto <matz@...> 2006/06/07

Hi,
[#7970] Re: [Bug?] set_trace_func: binding has wrong self value for return events — Florian Gross <florgro@...> 2006/06/07

Yukihiro Matsumoto wrote:

[#7929] RDoc --force flag — Vincent Fourmond <vincent.fourmond@9online.fr>

1 message 2006/05/27

[#7930] FOR SALE:nokia 8800,6600,n92,91,90,80,70 and Plas EDTV samsung at just $200 — noreply@...

Bugs item #4601, was opened at 2006-05-29 17:35

2 messages 2006/05/29
[#7932] Re: [ ruby-Bugs-4601 ] FOR SALE:nokia 8800,6600,n92,91,90,80,70 and Plas EDTV samsung at just $200 — Tom Copeland <tom@...> 2006/05/30

On Tue, 2006-05-30 at 02:35 +0900, noreply@rubyforge.org wrote:

[#7931] Critical 1.9 mathn bug (require 'mathn' failure) — noreply@...

Bugs item #4605, was opened at 2006-05-29 18:40

2 messages 2006/05/29
[#7933] Re: [ ruby-Bugs-4605 ] Critical 1.9 mathn bug (require 'mathn' failure) — Yukihiro Matsumoto <matz@...> 2006/05/30

Hi,

[#7934] round trip failure with YAML; both ruby_1_8 and HEAD — Mauricio Fernandez <mfp@...>

I caught syck corrupting data once again, and traced it down to this:

2 messages 2006/05/31
[#7935] Re: [BUG] round trip failure with YAML; both ruby_1_8 and HEAD — MenTaLguY <mental@...> 2006/05/31

On Thu, 1 Jun 2006 00:25:26 +0900, Mauricio Fernandez <mfp@acm.org> wrote:

Re: Possible YAMl bug in 1.8.4

From: damphyr@...
Date: 2006-05-09 12:20:19 UTC
List: ruby-core #7849 
Sorry for not quoting, but my webmail spits Base64 :)
Well, can somebody test my snippet with a 1.8.4 installation other than the one for Windows?
I don't know if James is on Windows and he was the one who stumbled on this behaviour, so it might be that it is still an outstanding YAML bug.
Cheers,
V.-

In This Thread

Prev Next