Ruby

=begin
Using quotes or not around the filename, it still crashes.

trunk does too.

1.8.7 does not:

type "s[s"
puts "hi"

ruby -v "s[s"
ruby 1.8.7 (2010-08-16 patchlevel 302) [i386-mingw32]
hi

=end

=begin

On Sep 19, 2010, at 20:05 , Luis Lavena wrote:

Issue #3851 has been updated by Luis Lavena.

Using quotes or not around the filename, it still crashes.

trunk does too.

1.8.7 does not:

type "s[s"
puts "hi"

ruby -v "s[s"
ruby 1.8.7 (2010-08-16 patchlevel 302) [i386-mingw32]
hi

This doesn't reproduce on OSX. If I had to guess, prolly not on any unix/linux.

Passed: 1.9.2-p0, 1.9.1-p129, 1.8.6-p399, 1.8.7-p302

=end

=begin
On Mon, Sep 20, 2010 at 12:43 AM, Ryan Davis ryand-ruby@zenspider.com wrote:

This doesn't reproduce on OSX. If I had to guess, prolly not on any unix/linux.

Passed: 1.9.2-p0, 1.9.1-p129, 1.8.6-p399, 1.8.7-p302

Nor on Linux, this seems strictly related to argument parsing on
Windows as this works:

ruby -I. -ve "load 's[s'"
ruby 1.9.2p0 (2010-08-18) [i386-mingw32]
hi

--
Luis Lavena
AREA 17¶

Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

=end

=begin
I think this must be a bug.

Here is a patch for the trunk:

--- dir.c 2010-09-20 14:12:13.000000000 +0900
+++ dir.c.new 2010-09-20 14:12:56.000000000 +0900
@@ -120,6 +120,7 @@
if (!*t1)
return NULL;
p = t1 + (r = rb_enc_mbclen(t1, pend, enc));

•  if (!*p) return NULL; if (p[0] == '-' && p[1] != ']') { const char *t2 = p + 1; int r2; 

=end

=begin
I actually ran across the problem by mistyping.

rspec spec/ as rspec s[ec/

ruby [foo
crash

ruby fo[
ruby: No such file or directory -- fo[ (LoadError)

ruby fo[o
ruby: No such file or directory -- fo[o (LoadError)

ruby a[o
crash

ruby f[o
ruby: No such file or directory -- f[o (LoadError)

ruby foo[bar
ruby: No such file or directory -- foo[bar (LoadError)

Seems to happen if [ is in positions 1 or 2 and follows particular characters like s or a as above.
Encoding issue?

=end