[#17566] rubychecker - runs checks on a Ruby interpreter — Igal Koshevoy <igal@...>

I've put together a shell script that runs checks on a Ruby interpreter.

14 messages 2008/07/03

[#17615] [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...>

At the moment, ruby-mode.el uses font-lock-keywords as opposed to

22 messages 2008/07/05
[#17657] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Yukihiro Matsumoto <matz@...> 2008/07/08

[#17678] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/09

It was designed to fix the following case:

[#17755] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/13

Here's a third patch that fixes a bug in the second and uses a quicker

[#17772] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/15

One more patch which fixes a few bugs in the the last one.

[#17773] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/15

Hi,

[#17776] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/15

Looks like version 22 doesn't support explicitly numbered regexp groups.

[#17779] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/15

Hi,

[#17783] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/15

Hi,

[#17788] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nathan Weizenbaum <nex342@...> 2008/07/15

Alright, here's a version that fixes both the highlighting bug and the

[#17793] Re: [PATCH] ruby-mode.el: Fix here-doc strings with inner quotes — Nobuyoshi Nakada <nobu@...> 2008/07/16

Hi,

[#17644] Features to be included in Ruby 1.9.1 — "Yugui (Yuki Sonoda)" <yugui@...>

Hi, all

27 messages 2008/07/08

[#17674] [Ruby 1.8 - Bug #238] (Open) Ruby doesn't respect the Windows read-only flag — Jim Deville <redmine@...>

Issue #238 has been reported by Jim Deville.

10 messages 2008/07/08

[#17708] [Ruby 1.8 - Bug #252] (Open) Array#sort doesn't respect overridden <=> — Ryan Davis <redmine@...>

Issue #252 has been reported by Ryan Davis.

13 messages 2008/07/09

[#17871] duping the NilClass — "Nasir Khan" <rubylearner@...>

While nil is an object, calling dup on it causes TypeError. This doesnt seem

33 messages 2008/07/20
[#17872] Re: duping the NilClass — Urabe Shyouhei <shyouhei@...> 2008/07/20

Nasir Khan wrote:

[#17873] Re: duping the NilClass — "Meinrad Recheis" <meinrad.recheis@...> 2008/07/20

On Sun, Jul 20, 2008 at 7:55 PM, Urabe Shyouhei <shyouhei@ruby-lang.org>

[#17877] Re: duping the NilClass — Urabe Shyouhei <shyouhei@...> 2008/07/20

Meinrad Recheis wrote:

[#17879] Re: duping the NilClass — Kurt Stephens <ks@...> 2008/07/20

Urabe Shyouhei wrote:

[#17880] Re: duping the NilClass — "Nasir Khan" <rubylearner@...> 2008/07/21

I write a lot of hand crafted dup or clone because I want control as well as

[#17881] Re: duping the NilClass — "David A. Black" <dblack@...> 2008/07/21

Hi --

[#17882] Re: duping the NilClass — Urabe Shyouhei <shyouhei@...> 2008/07/21

+1 to David. A convenient way to do Marshal idiom should be a new

[#17885] Re: duping the NilClass — "Robert Dober" <robert.dober@...> 2008/07/21

On Mon, Jul 21, 2008 at 8:21 AM, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#17887] Re: duping the NilClass — "David A. Black" <dblack@...> 2008/07/21

Hi --

[#17889] Re: duping the NilClass — "Robert Dober" <robert.dober@...> 2008/07/21

On Mon, Jul 21, 2008 at 1:02 PM, David A. Black <dblack@rubypal.com> wrote:

[#17883] [Ruby 1.9 - Bug #340] (Open) 1.9/trunk does not work when compiled with llvm-gcc4 2.3 (gcc 4.2.1) — Ollivier Robert <redmine@...>

Issue #340 has been reported by Ollivier Robert.

14 messages 2008/07/21

[#17943] RUBY_ENGINE? — "Vladimir Sizikov" <vsizikov@...>

Hi,

56 messages 2008/07/24
[#17950] Re: RUBY_ENGINE? — Tanaka Akira <akr@...> 2008/07/25

In article <3454c9680807241200xf7cc766qb987905a3987bb78@mail.gmail.com>,

[#17958] Re: RUBY_ENGINE? — "Vladimir Sizikov" <vsizikov@...> 2008/07/25

Hi,

[#17981] Re: RUBY_ENGINE? — Tanaka Akira <akr@...> 2008/07/26

In article <3454c9680807250054i70db563duf44b42d92ba41bfb@mail.gmail.com>,

[ruby-core:18036] Re: New array methods cycle, choice, shuffle (plus bug in cycle)

From: Charles Oliver Nutter <charles.nutter@...>
Date: 2008-07-31 23:33:15 UTC
List: ruby-core #18036
Restarting this thread because I missed it the first time around and 
because I agree it should be "choose" rather than "choice" if it's going 
to be in. Also, it doesn't appear to have been settled the first time.

choice is a noun. choose, map, select, collect, etc are imperative 
verbs. So choose much more consistent with the others. Also, choice 
implies to me that it's already been made...since you can't have a 
choice unless you've already made a "choice". In essence, a "choice" is 
the product of "choosing" something. So ary.choose produces a choice.

- Charlie

David Flanagan wrote:
> Four new methods have been added to Array the Ruby 1.9 trunk.  I've got 
> a couple of questions and comments and one bug report:
> 
> cycle is an iterator that is like calling each on the array within an 
> infinite loop. Matz: have you considered generalizing this to be a 
> method of Enumerable?
> 
> cycle has what I'd consider a bug: call it on an empty array and it will 
> never return and will never invoke the associated block.
> 
>     ruby1.9 -e '[].cycle {}'
> 
> When I do this I can't even ^C to stop ruby. I have to kill -9 the 
> process. I'd suggest that cycle simply return when the array is empty. 
> That is, it cycles until the array becomes empty (which will be forever 
> in most cases).  The patch I propose is at the bottom of this message.
> 
> choice returns a random element from the array.  I don't like the name 
> of this method: neither the word "choice" nor it verb form "choose" 
> imply randomness--instead they suggest the opposite.  I suggest just 
> using the name "rand", "random" or "random_element". Most array methods 
> are verbs, but a noun here would match the existing methods first and 
> last.  Also, may I suggest a random! variant of the method that returns 
> *and removes* a random element from the array?  first and last already 
> have shift and pop to serve this purpose.
> 
> shuffle and shuffle! randomly permute an array and seem worth having.  I 
> think I remember Josh Bloch (author of the Java collections library) 
> writing somewhere that shuffling an array correctly is actually kind of 
> hard to do, so I think it is great to have these methods, even if I 
> can't think of a use case right now :-)
> 
>     David
> 
> --- array.c.orig        2007-09-06 15:00:02.000000000 -0700
> +++ array.c     2007-09-06 15:03:30.000000000 -0700
> @@ -2940,6 +2940,7 @@
> 
>      RETURN_ENUMERATOR(ary, 0, 0);
>      for (;;) {
> +       if (RARRAY_LEN(ary) == 0) return Qnil;
>         for (i=0; i<RARRAY_LEN(ary); i++) {
>             rb_yield(RARRAY_PTR(ary)[i]);
>         }
> 
> 


In This Thread