[#3907] Obtaining mode information on an IO object — Jos Backus <jos@...>

The attached patch implements IO#mode. This method returns the mode the IO

17 messages 2004/12/06
[#3909] Re: [patch] Obtaining mode information on an IO object — nobu.nokada@... 2004/12/07

Hi,

[#3910] Re: [patch] Obtaining mode information on an IO object — Jos Backus <jos@...> 2004/12/07

On Tue, Dec 07, 2004 at 09:25:13AM +0900, nobu.nokada@softhome.net wrote:

[#3925] Re: [patch] Obtaining mode information on an IO object — James Britt <ruby@...> 2004/12/09

Jos Backus wrote:

[#4009] cgi.rb -- more GET/POST stuff — mde@...26.com

First of all, I think it would be great, as Eustaquio suggests, to

17 messages 2004/12/23
[#4016] Re: [PATCH] cgi.rb -- more GET/POST stuff — Francis Hwang <sera@...> 2004/12/24

GETs and POSTs are defined to be fairly different actions. I'd read

[#4027] Allowing custom number literal suffixes? — Florian Gro<florgro@...>

Moin!

35 messages 2004/12/27
[#4070] Re: Allowing custom number literal suffixes? — nobu.nokada@... 2005/01/02

Hi,

[#4072] Re: Allowing custom number literal suffixes? — Mathieu Bouchard <matju@...> 2005/01/02

[#4079] Re: Allowing custom number literal suffixes? — Florian Gro<florgro@...> 2005/01/03

Mathieu Bouchard wrote:

[#4081] Re: Allowing custom number literal suffixes? — Mathieu Bouchard <matju@...> 2005/01/03

[#4082] Re: Allowing custom number literal suffixes? — Florian Gro<florgro@...> 2005/01/03

Mathieu Bouchard wrote:

[#4084] Re: Allowing custom number literal suffixes? — Brent Roman <brent@...> 2005/01/04

I'm not sure I would advocate making Ruby's grammar even more

[#4086] Re: Allowing custom number literal suffixes? — Mathieu Bouchard <matju@...> 2005/01/04

[#4033] Garbage collection trouble — Christian Neukirchen <chneukirchen@...>

Hello,

13 messages 2004/12/27

Re: [PATCH] Marshal.dump'ing OpenStruct objects

From: nobu.nokada@...
Date: 2004-12-03 01:21:21 UTC
List: ruby-core #3868
Hi,

At Thu, 2 Dec 2004 09:38:31 +0900,
Yukihiro Matsumoto wrote in [ruby-core:03863]:
> |I think this allows one to dump OpenStruct objects, and addresses the
> |data compatibility issue:
> 
> I have recently restored the old behavior, but this one seems
> superior.  I will take this.

This change makes no sense as for the compatibility.

  $ cvs up -A lib/ostruct.rb
  U lib/ostruct.rb
  $ ./ruby -rostruct -e 'o=OpenStruct.new;o.foo=1;print Marshal.dump(o)' > ostruct.dump
  $ od -tx1z ostruct.dump
  0000000 04 08 65 3a 1a 4f 70 65 6e 53 74 72 75 63 74 3a  >..e:.OpenStruct:<
  0000020 3a 4d 61 72 73 68 61 6c 65 72 55 3a 0f 4f 70 65  >:MarshalerU:.Ope<
  0000040 6e 53 74 72 75 63 74 6f 3b 06 06 3a 0b 40 74 61  >nStructo;..:.@ta<
  0000060 62 6c 65 7b 06 3a 08 66 6f 6f 69 06              >ble{.:.fooi.<
  0000074
  $ cvs up -r1.11 lib/ostruct.rb
  U lib/ostruct.rb
  $ ./ruby -rostruct -e 'p Marshal.load(STDIN)' < ostruct.dump
  -e:1:in `load': undefined class/module OpenStruct::Marshaler (ArgumentError)
          from -e:1

It is same as simply adding marshal_dump/marhsal_load.

-- 
Nobu Nakada

In This Thread