[#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:01401] Re: Bignum aset

From: gotoken@... (GOTO Kentaro)
Date: 2000-02-15 21:18:02 UTC
List: ruby-talk #1401
In message "[ruby-talk:01398] Bignum aset"
    on 00/02/15, Andrew Hunt <Andy@Toolshed.Com> writes:

>In class Bignum, there is a very handy method for bit reference ([]).
>But there is no corresponding bit setter ([]=).
>
>Is this deliberate?  I need an abritrarily large pile of bits to set and
>test, and this seems like the right place to do it.  Should I be using
>some different class instead?

Yes, I heard it is deliberate.  An instance of Numeric is a unique
object corresponding to a numeric. And, []= is usually a destructive
method.

Now, for example, imagine what happens by `2[0] = 1'.  Will 2 be 3?

So, we can see that this comes from same reason of the lack of ++
operator.

Regards,

-- gotoken

In This Thread