[#407] New feature for Ruby? — Clemens.Hintze@...
Hi all,
27 messages
1999/07/01
[#413] Re: New feature for Ruby?
— matz@... (Yukihiro Matsumoto)
1999/07/01
Hi Clemens,
[#416] Re: New feature for Ruby?
— Clemens Hintze <c.hintze@...>
1999/07/01
On Thu, 01 Jul 1999, Yukihiro Matsumoto wrote:
[#418] Re: New feature for Ruby?
— gotoken@... (GOTO Kentaro)
1999/07/01
Hi
[#426] Re: New feature for Ruby?
— gotoken@... (GOTO Kentaro)
1999/07/02
Hi,
[#427] Re: New feature for Ruby?
— Clemens Hintze <c.hintze@...>
1999/07/02
On Fri, 02 Jul 1999, you wrote:
[#428] Re: New feature for Ruby?
— gotoken@... (GOTO Kentaro)
1999/07/03
Hi,
[#429] Re: New feature for Ruby?
— Clemens Hintze <c.hintze@...>
1999/07/03
On Sat, 03 Jul 1999, you wrote:
[#430] Re: New feature for Ruby?
— gotoken@... (GOTO Kentaro)
1999/07/05
Hi,
[#431] Re: New feature for Ruby?
— Clemens Hintze <c.hintze@...>
1999/07/07
On Mon, 05 Jul 1999, you wrote:
[#440] Now another totally different ;-) — Clemens Hintze <c.hintze@...>
Hi,
21 messages
1999/07/09
[#441] Re: Now another totally different ;-)
— matz@... (Yukihiro Matsumoto)
1999/07/09
Hi,
[#442] Re: Now another totally different ;-)
— Clemens Hintze <c.hintze@...>
1999/07/09
On Fri, 09 Jul 1999, you wrote:
[#452] Re: Now another totally different ;-)
— gotoken@... (GOTO Kentaro)
1999/07/11
Hi,
[#462] Re: Now another totally different ;-)
— matz@... (Yukihiro Matsumoto)
1999/07/12
Hello, there.
[#464] Re: Now another totally different ;-)
— Clemens Hintze <c.hintze@...>
1999/07/12
On Mon, 12 Jul 1999, you wrote:
[#467] Re: Now another totally different ;-)
— matz@... (Yukihiro Matsumoto)
1999/07/12
Hi,
[#468] Re: Now another totally different ;-)
— gotoken@... (GOTO Kentaro)
1999/07/12
In message "[ruby-talk:00467] Re: Now another totally different ;-)"
[#443] — Michael Hohn <hohn@...>
Hello,
26 messages
1999/07/09
[#444] interactive ruby, debugger
— gotoken@... (GOTO Kentaro)
1999/07/09
Hi Michael,
[#448] Re: interactive ruby, debugger
— "NAKAMURA, Hiroshi" <nakahiro@...>
1999/07/10
Hi,
[#450] Re: interactive ruby, debugger
— Clemens Hintze <c.hintze@...>
1999/07/10
On Sat, 10 Jul 1999, you wrote:
[#490] Some questions concerning GC in Ruby extensions — Clemens Hintze <c.hintze@...>
Hi matz,
6 messages
1999/07/14
[#501] Ruby 1.3.5 — Yukihiro Matsumoto <matz@...>
Ruby 1.3.5 is out, check out:
1 message
1999/07/15
[#519] CGI.rb — "Michael Neumann" <neumann@...>
Hi...
7 messages
1999/07/24
[#526] Another way for this? And a new proposal! — Clemens Hintze <c.hintze@...>
Hi,
6 messages
1999/07/25
[ruby-talk:00480] Re: Now another totally different ;-)
From:
Clemens Hintze <c.hintze@...>
Date:
1999-07-13 16:08:28 UTC
List:
ruby-talk #480
On Tue, 13 Jul 1999, you wrote: >In message "[ruby-talk:00471] Re: Now another totally different ;-)" > on 99/07/12, Clemens Hintze <c.hintze@gmx.net> writes: [...] >I see. Your opinion also seems right. The matter to consider may be >the degree of benefit in daily programming. That is, how general >enumerable classes become convenient by Enumerable#[]. I often was gone thru the lacks-a-nail school :-))) But, of course, you have found the point to be considered! [...] >Under my own criterion, Only File and Range are naturally will be held >x.to_a[i] == x[i]. IO and Dir are not suitable to be so, because IO >is nondeterministic, dir[i] is just not natural. Agree. > >The above discussion may be not enough to decide to reject Cle's >Enumerable#[], but I feel such [] is too special yet. Perhaps it is. :-) I was only so obstinate, as I have got the feeling, that the proposal would be rejected without deeply understand my reasons. Sorry if I was wrong! :-} But now, as I have explained all my reasons, and they are understood by you, I will step back and look what you all decide for that proposal. :-) But please be consistent. If the decision is not to have `Enumerable#[]' please also remove `Enumerable#index'. As I think all reasons FOR implementing `index' are also valid for `[]' and all AGAINST `[]' are also true against `index'. BTW: Has anybody already had a look onto my class Sequence, posted some days before? Are there already decisions, whether it should not be made into a new class, but be put into class Range? If not, would class Sequence become part of the standard distribution? Sorry for seeming unpatient. I only try to keep you sleepless ;-)))) [...] >I'm being amazed how many you you make new proporsals! =) I have some new ones behind my back! But don't hold breath! ;-))) > >-- gotoken \cle