[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>

33 messages 2000/02/08

[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>

Conrad writes:

13 messages 2000/02/15

[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>

17 messages 2000/02/19
[#1544] Re: Ruby/GTK and the mainloop — Yasushi Shoji <yashi@...> 2000/02/23

Hello Ian,

[#1550] Re: Ruby/GTK and the mainloop — Ian Main <imain@...> 2000/02/23

On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:

[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>

((FYI: This was sent to the Ruby mail list.))

10 messages 2000/02/19

[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>

The following message is a courtesy copy of an article

12 messages 2000/02/25

[ruby-talk:01393] Re: Say Hi

From: mengx@...
Date: 2000-02-15 18:54:25 UTC
List: ruby-talk #1393
> I think `insert' may be a good choice.
> What do you guys think about adding this method to Array?
> And possibly `insert_after' to make emulating `push' easier.

How about a pair insert_before/insert_after. This would take care of
all additions. String(and other Sequence types) could also use them.
 
> 
> In addition, should inserting array be treated specially?  E.g.
> 
>   [1,2,3].insert(0,[5,6])         #=> [[5,6],1,2,3] or [5,6,1,2,3]
> 

How about a pair group_insert_before/group_insert_after which leads to 
the latter. This would save the for loop.

Thanks

-Ted Meng

In This Thread

Prev Next