[#2332] Ruby-Python fusion? — mrilu <mrilu@...>
Usually I give some time for news to settle before I pass the word, but
7 messages
2000/04/01
[#2353] Re: Function of Array.filter surprises me — schneik@...
5 messages
2000/04/03
[#2361] crontab — Hugh Sasse Staff Elec Eng <hgs@...>
I want to have a program that may be run between certain times.
11 messages
2000/04/05
[#2375] Marshal: Want string out, but want depth specified? — Hugh Sasse Staff Elec Eng <hgs@...>
@encoded = [Marshal.dump(@decoded, , depth)].pack("m")
7 messages
2000/04/07
[#2378] Re: Marshal: Want string out, but want depth specified?
— matz@... (Yukihiro Matsumoto)
2000/04/07
Hi,
[#2376] Iterator into array — Dave Thomas <Dave@...>
15 messages
2000/04/07
[#2397] Could missing 'end' be reported better? — mrilu <mrilu@...>
I'm not sure one could easily parse, or moreover report, this error better.
5 messages
2000/04/08
[#2404] Re: Iterator into array — Andrew Hunt <andy@...>
>It's still possible to introduce a new syntax for collecting yielded
6 messages
2000/04/08
[#2412] Re: Could missing 'end' be reported better? — h.fulton@...
7 messages
2000/04/09
[#2414] Re: Could missing 'end' be reported better?
— matz@... (Yukihiro Matsumoto)
2000/04/09
Hi,
[#2429] Please join me, I'm Hashing documentation — mrilu <mrilu@...>
This is a story about my hashing ventures, try to bear with me.
5 messages
2000/04/10
[#2459] Precedence question — Dave Thomas <Dave@...>
7 messages
2000/04/12
[#2474] Ruby 1.4.4 — Yukihiro Matsumoto <matz@...>
Ruby 1.4.4 is out, check out:
5 messages
2000/04/14
[#2494] ANNOUNCE : PL/Ruby — ts <decoux@...>
7 messages
2000/04/17
[#2514] frozen behavior — Andrew Hunt <Andy@...>
7 messages
2000/04/19
[#2530] Re: 'in' vs. 'into' — Andrew Hunt <andy@...>
>Hmm, I've not decided yet. Here's the list of options:
6 messages
2000/04/20
[#2535] Default naming for iterator parameters — mrilu <mrilu@...>
I'm back at my computer after some traveling. I know I think Ruby
5 messages
2000/04/20
[#2598] different thread semantics 1.4.3 -> 1.4.4 — hipster <hipster@...4all.nl>
Hi fellow rubies,
4 messages
2000/04/28
[ruby-talk:02577] Re: String.succ
From:
mrilu <mrilu@...>
Date:
2000-04-26 08:53:43 UTC
List:
ruby-talk #2577
> In message "[ruby-talk:02575] String.succ"
> on 00/04/26, Dave Thomas <Dave@thomases.com> writes:
>
> | "\377".succ # -> "\000"
> |
> |I _think_ I'd expect "\001\000".
Me too.
On Wed, 26 Apr 2000, Yukihiro Matsumoto wrote:
> Ok, I define as following:
>
> "".succ == ""
> "\377".succ == "\001\000"
Sounds good.
> I'll submit a patch in few days. Magic increment for binary strings
> are done only if they contain no alpha numeric character.
Everytime I hear magic associated with code I smile. Until I recognize it's
not a status issue but really relates to the inner working of the code.
I feel there's two different functionalities here, and the difference should
be made clear. That allows one to use .succ without knowing "special cases".
So the functionalities are:
1) succ as just defined, returning successing element into infinity
- with numbers generate every time num+1
- with strings generates longer and longer strings as defined
2) succ as loopingly iterating over some space:
- with strings, "\377".succ -> "\000", "\377\377".succ -> "\000\000"
- object.succ(range) (possibly)
As we have strings in two different classes I think those differentces should
be make explicit. We could rename the second class (like next).
Other solution could be to define class AlphaNumericString < String and
overwrite succ. The problem here is that this class' unnatural, magically not
incrementing succ should be renamed anyway :).
Btw. the current implementation (1.5.quite_new)
"\377\377".succ -> "\377\000"
which does not fit into previous functionality classes and surprises me
anyway. Should we have more functionality classes?