[#6363] Re: rescue clause affecting IO loop behavior — ts <decoux@...>

>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:

17 messages 2000/11/14
[#6367] Re: rescue clause affecting IO loop behavior — David Alan Black <dblack@...> 2000/11/14

Hello again --

[#6582] best way to interleaf arrays? — David Alan Black <dblack@...>

Hello --

15 messages 2000/11/26

[#6646] RE: Array Intersect (&) question — Aleksi Niemel<aleksi.niemela@...>

Ross asked something about widely known and largely ignored language (on

23 messages 2000/11/29
[#6652] RE: Array Intersect (&) question — rpmohn@... (Ross Mohn) 2000/11/29

aleksi.niemela@cinnober.com (Aleksi Niemel) wrote in

[#6723] Re: Array Intersect (&) question — Mathieu Bouchard <matju@...> 2000/12/01

> >Use a hash. Here's code to do both and more. It assumes that

[#6656] printing/accessing arrays and hashes — raja@... (Raja S.)

I'm coming to Ruby with a Python & Common Lisp background.

24 messages 2000/11/30

[ruby-talk:6594] Re: best way to interleaf arrays?

From: Dave Thomas <Dave@...>
Date: 2000-11-27 22:29:52 UTC
List: ruby-talk #6594
David Alan Black <dblack@candle.superlink.net> writes:

> What about a to_h method for arrays?  I mention this mainly for the
> sake of symmetry with other to_* methods.  Then again, such a method
> may violate some principle of design: it does seem slightly wrong for
> Array to "know" how to generate a hash (whereas not strange for Hash
> to know how to create itself from an array).

That was my thinking (if you can call it that ;-) It seems reasonable
for a more complex class to know about a more primitive one, but not
the other way around.

An alternative might be  Kernel::Hash, along the lines of
Kernel::Integer, which does the business depending on the type of its
argument.


Regards


Dave

In This Thread