[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5652] Array#insert

From: Aleksi Niemel<aleksi.niemela@...>
Date: 2000-10-17 20:18:00 UTC
List: ruby-talk #5652
I was looking up how Array#insert should be called. Uh, there's none! Maybe
there's some other suitable method somewhere in the middle of the other, but
I didn't spot it fast.

Of course ary[index,0] = stuff. But it's very annoying format, when you
could be more explicit too. Besides there's always the surprise of

  ruby -e'a=[1,2,3]; a[1,0]=[4,5]; p a;'
  [1, 4, 5, 2, 3]
  ruby -e'a=[1,2,3]; a[1,0]=[[4,5]]; p a;'
  [1, [4, 5], 2, 3]

lurking, and I'd expect the first example output what the second does.

If there should be Array#insert we should probably make up our mind whether
it should be implemented as (not any real code, just to show possible few
points for debate)

  class Array
    def insert(index, *ary)
      self[index<+1>, 0] = <*>ary
    end
  end

where <+1> is about having semantics of "insert-before/at" or "insert-after"
index, and <*> if there should be some sort of autoflattening, or in some
other form. I personally don't have opinion should the semantics be before
or after, but I'd expect Array#insert not to autoflatten in any way.

	- Aleksi

In This Thread

Prev Next