[#21039] Happy new year and... moving Ruby development to Git? — Michael Klishin <michael.s.klishin@...>

Happy new year everyone.

94 messages 2009/01/01
[#21040] Re: Happy new year and... moving Ruby development to Git? — James Gray <james@...> 2009/01/01

On Jan 1, 2009, at 6:42 AM, Michael Klishin wrote:

[#21041] Re: Happy new year and... moving Ruby development to Git? — brabuhr@... 2009/01/01

On Thu, Jan 1, 2009 at 11:22 AM, James Gray <james@grayproductions.net> wrote:

[#21042] Re: Happy new year and... moving Ruby development to Git? — Federico Builes <federico.builes@...> 2009/01/01

brabuhr@gmail.com writes:

[#21049] Re: Happy new year and... moving Ruby development to Git? — Michael Klishin <michael.s.klishin@...> 2009/01/01

[#21053] Re: Happy new year and... moving Ruby development to Git? — znmeb@... 2009/01/01

Quoting Michael Klishin <michael.s.klishin@gmail.com>:

[#21068] Re: Happy new year and... moving Ruby development to Git? — Yukihiro Matsumoto <matz@...> 2009/01/02

Hi,

[#21069] Re: Happy new year and... moving Ruby development to Git? — Florian Gilcher <flo@...> 2009/01/02

-----BEGIN PGP SIGNED MESSAGE-----

[#21070] Re: Happy new year and... moving Ruby development to Git? — "Luis Lavena" <luislavena@...> 2009/01/02

On Fri, Jan 2, 2009 at 12:18 PM, Florian Gilcher <flo@andersground.net> wrote:

[#21073] Re: Happy new year and... moving Ruby development to Git? — mathew <meta@...> 2009/01/02

My opinion:

[#21078] Re: Happy new year and... moving Ruby development to Git? — "Eust痃uio Rangel" <eustaquiorangel@...> 2009/01/02

My two cents:

[#21101] Re: Happy new year and... moving Ruby development to Git? — "M. Edward (Ed) Borasky" <znmeb@...> 2009/01/03

Eust痃uio Rangel wrote:

[#21102] Re: Happy new year and... moving Ruby development to Git? — "Nikolai Weibull" <now@...> 2009/01/03

On Sat, Jan 3, 2009 at 21:40, M. Edward (Ed) Borasky <znmeb@cesmail.net> wrote:

[#21104] Re: Happy new year and... moving Ruby development to Git? — "M. Edward (Ed) Borasky" <znmeb@...> 2009/01/03

Nikolai Weibull wrote:

[#21106] Re: Happy new year and... moving Ruby development to Git? — "Giuseppe Bilotta" <giuseppe.bilotta@...> 2009/01/04

On Sat, Jan 3, 2009 at 10:39 PM, M. Edward (Ed) Borasky

[#21114] Re: Happy new year and... moving Ruby development to Git? — Joel VanderWerf <vjoel@...> 2009/01/04

Giuseppe Bilotta wrote:

[#21132] Re: Happy new year and... moving Ruby development to Git? — Michael Klishin <michael.s.klishin@...> 2009/01/05

[#21134] Re: Happy new year and... moving Ruby development to Git? — Daniel Berger <djberg96@...> 2009/01/05

Michael Klishin wrote:

[#21080] Re: Happy new year and... moving Ruby development to Git? — Eric Hodel <drbrain@...7.net> 2009/01/02

On Jan 1, 2009, at 04:42 AM, Michael Klishin wrote:

[#21083] Re: Happy new year and... moving Ruby development to Git? — "Nikolai Weibull" <now@...> 2009/01/03

On Sat, Jan 3, 2009 at 00:34, Eric Hodel <drbrain@segment7.net> wrote:

[#21160] Re: Happy new year and... moving Ruby development to Git? — Eric Hodel <drbrain@...7.net> 2009/01/05

On Jan 2, 2009, at 17:25 PM, Nikolai Weibull wrote:

[#21165] Re: Happy new year and... moving Ruby development to Git? — Sylvain Joyeux <sylvain.joyeux@...4x.org> 2009/01/06

> I think I'm entitled to an opinion on the subject because I am a

[#21089] Re: Happy new year and... moving Ruby development to Git? — Michael Klishin <michael.s.klishin@...> 2009/01/03

[#21147] Re: Happy new year and... moving Ruby development to Git? — Paul Brannan <pbrannan@...> 2009/01/05

On Sat, Jan 03, 2009 at 12:48:09PM +0900, Michael Klishin wrote:

[#21097] [Bug #977] caller for all threads patch — Roger Pack <redmine@...>

Bug #977: caller for all threads patch

15 messages 2009/01/03
[#23760] Re: [Bug #977] caller for all threads patch — SASADA Koichi <ko1@...> 2009/06/08

I made a patch to Thread#caller(lev=1). It may be more flexible than

[#21244] [Bug #999] SSL & ZIP missing from ruby-1.9.1-preview1-i386-mswin32 — William Mason <redmine@...>

Bug #999: SSL & ZIP missing from ruby-1.9.1-preview1-i386-mswin32

14 messages 2009/01/10

[#21259] Do I need a special build arg to get irb to accept utf characters on OSX — Dave Thomas <dave@...>

I'm seeing very strange behavior at the irb prompt with ruby 1.9.1

10 messages 2009/01/11

[#21289] MRI 1.8.6 bug - exit is ignored if ensure clause throws exception which is caught by outer rescue — Shri Borde <Shri.Borde@...>

The following code snippet does print "after foo" when using MRI 1.8.6 on Windows Vista, showing that exit is ignored. Any thoughts on whether this is by design, a known bug, or a new issue? If it's the latter, should I open a bug for it?

5 messages 2009/01/12

[#21310] [Bug #1008] Missing shell version of ruby-1.9 commands (gem, rake, ...) for MinGW installation — Chauk-Mean Proum <redmine@...>

Bug #1008: Missing shell version of ruby-1.9 commands (gem, rake, ...) for MinGW installation

8 messages 2009/01/13

[#21339] [Bug #1010] Ruby-1.9's rake sh doesn't work on Windows (but fix provided) — Chauk-Mean Proum <redmine@...>

Bug #1010: Ruby-1.9's rake sh doesn't work on Windows (but fix provided)

10 messages 2009/01/14

[#21399] Proposal: Module#copy_method — Yehuda Katz <wycats@...>

I'd like it to be possible to copy methods from one module to another. The

38 messages 2009/01/18
[#21428] Re: Proposal: Module#copy_method — Yukihiro Matsumoto <matz@...> 2009/01/19

Hi,

[#21550] [Feature #1046] request: ability to run without specifying .rb — Roger Pack <redmine@...>

Feature #1046: request: ability to run without specifying .rb

13 messages 2009/01/24

[#21552] [Feature #1047] request: getters, setters for the GC — Roger Pack <redmine@...>

Feature #1047: request: getters, setters for the GC

15 messages 2009/01/24

[#21613] [Bug #1063] in `write': Not enough space - <STDOUT> (Errno::ENOMEM) on Windows XP — Nick Gorbikoff <redmine@...>

Bug #1063: in `write': Not enough space - <STDOUT> (Errno::ENOMEM) on Windows XP

11 messages 2009/01/27

[#21640] [Bug #1068] Ruby Cannot Handle Some UIDs — James Gray <redmine@...>

Bug #1068: Ruby Cannot Handle Some UIDs

12 messages 2009/01/28
[#21642] Re: [Bug #1068] Ruby Cannot Handle Some UIDs — Ondrej Bilka <neleai@...> 2009/01/28

On Wed, Jan 28, 2009 at 05:00:05PM +0100, James Gray wrote:

[#21663] Re: [Bug #1068] Ruby Cannot Handle Some UIDs — Nobuyoshi Nakada <nobu@...> 2009/01/29

Hi,

[#21701] [Feature #1081] add File::write() convenience method — Suraj Kurapati <redmine@...>

Feature #1081: add File::write() convenience method

34 messages 2009/01/31
[#28450] [Feature #1081] add File::write() convenience method — Yusuke Endoh <redmine@...> 2010/03/03

Issue #1081 has been updated by Yusuke Endoh.

[#28455] Re: [Feature #1081] add File::write() convenience method — Yukihiro Matsumoto <matz@...> 2010/03/04

Hi,

[#28472] Re: [Feature #1081] add File::write() convenience method — Yusuke ENDOH <mame@...> 2010/03/04

Hi,

[#21702] [Feature #1082] add Object#singleton_class method — Suraj Kurapati <redmine@...>

Feature #1082: add Object#singleton_class method

54 messages 2009/01/31
[#27372] [Feature #1082] add Object#singleton_class method — Suraj Kurapati <redmine@...> 2010/01/02

Issue #1082 has been updated by Suraj Kurapati.

[#27384] Re: [Feature #1082] add Object#singleton_class method — Yukihiro Matsumoto <matz@...> 2010/01/04

Hi,

[#27394] Re: [Feature #1082] add Object#singleton_class method — Yusuke ENDOH <mame@...> 2010/01/04

Hi,

[#27407] Re: [Feature #1082] add Object#singleton_class method — Shugo Maeda <shugo@...> 2010/01/05

Hi,

[#27409] Re: [Feature #1082] add Object#singleton_class method — Yukihiro Matsumoto <matz@...> 2010/01/05

Hi,

[#28304] Re: [Feature #1082] add Object#singleton_class method — Shugo Maeda <shugo@...> 2010/02/23

Hi,

[ruby-core:21690] [Bug #1074] crash on variable reference in BEGIN inside class

From: Yusuke Endoh <redmine@...>
Date: 2009-01-31 00:29:38 UTC
List: ruby-core #21690
Bug #1074: crash on variable reference in BEGIN inside class
http://redmine.ruby-lang.org/issues/show/1074

Author: Yusuke Endoh
Status: Open, Priority: Normal
Assigned to: Yukihiro Matsumoto, Category: core, Target version: 1.9.2
Reproducible Version: trunk, ruby -v: ruby 1.9.1p5000 (2009-01-31 trunk 21909) [i686-linux]

(auto-registration seemed to fail to register [ruby-core:21657]
 on redmine, so I do manually)


Hi,


2009/1/29 Soutaro Matsumoto <matsumoto@soutaro.com>:
> Hi,
>
> ruby 1.9 crashes on variable reference in BEGIN block inside class or
> block like the following.
>
>
>  class C
>    x = 10
>    BEGIN { puts x }
>  end
>
>  lambda {
>    x = 10
>    BEGIN { puts x }
>  }
>
>
> Prohibiting BEGIN in non-toplevel scope seems good for me.
>
>
> $ rubysvn --version
> ruby 1.9.1p5000 (2009-01-29 trunk 21874) [i386-darwin9.6.0]
>
> $ rubysvn
> class C
>  x = 10
>  BEGIN { puts x }
> end
>
> rubysvn: [BUG] get_local_var_idx: -1
> ruby 1.9.1p5000 (2009-01-29 trunk 21874) [i386-darwin9.6.0]
>
> -- control frame ----------
> c:0002 p:-587732 s:0004 b:0004 l:000003 d:000003 TOP
> c:0001 p:0000 s:0002 b:0002 l:000004 d:000004 TOP    <main>:54964
> ---------------------------
> -- Ruby level backtrace information-----------------------------------------
>
> -- C level backtrace information -------------------------------------------
> 0x119612 0   rubysvn                             0x00119612
> rb_vm_bugreport + 82
> 0x2cf6c 1   rubysvn                             0x0002cf6c rb_warning + 444
> 0x2cfcb 2   rubysvn                             0x0002cfcb rb_bug + 43
> 0xf3461 3   rubysvn                             0x000f3461
> rb_iseq_translate_threaded_code + 1345
> 0xf5a5c 4   rubysvn                             0x000f5a5c
> rb_parse_in_main + 3692
> 0xfdcf9 5   rubysvn                             0x000fdcf9
> rb_iseq_compile_node + 3193
> 0xfde1a 6   rubysvn                             0x000fde1a
> rb_iseq_compile_node + 3482
> 0xfee68 7   rubysvn                             0x000fee68
> rb_iseq_compile_node + 7656
> 0xf6b67 8   rubysvn                             0x000f6b67
> rb_parse_in_main + 8055
> 0xf84b3 9   rubysvn                             0x000f84b3
> rb_parse_in_main + 14531
> 0xfd4fc 10  rubysvn                             0x000fd4fc
> rb_iseq_compile_node + 1148
> 0x100dbb 11  rubysvn                             0x00100dbb
> ruby_debug_breakpoint + 3579
> 0x100e71 12  rubysvn                             0x00100e71
> rb_iseq_new_main + 97
> 0xbe7e6 13  rubysvn                             0x000be7e6 ruby_set_argv
> + 2326
> 0x108dff 14  rubysvn                             0x00108dff
> rb_vm_call_cfunc + 175
> 0xbea9d 15  rubysvn                             0x000bea9d
> ruby_process_options + 157
> 0x3210b 16  rubysvn                             0x0003210b ruby_options
> + 123
> 0x2147 17  rubysvn                             0x00002147 main + 87
> 0x20b6 18  rubysvn                             0x000020b6 start + 54
>
> [NOTE]
> You may encounter a bug of Ruby interpreter. Bug reports are welcome.
> For details: http://www.ruby-lang.org/bugreport.html


Thank you for your report, Soutaro.

I fixed this issue in r21876 by changing syntax to prohibit
BEGIN in non-toplevel scope.
At Yugui's discretion, the change is included in 1.9.1 release.


$ ruby -ve 'class Foo; BEGIN {}; end'
ruby 1.9.1p0 (2009-01-30 revision 21907) [i686-linux]
-e:1: syntax error, unexpected keyword_BEGIN
class Foo; BEGIN {}; end
                ^


Currently, the change is applied to only branches/ruby_1_9_1.
Matz, what do you think of it for trunk?

-- 
Yusuke ENDOH <mame@tsg.ne.jp>


----------------------------------------
http://redmine.ruby-lang.org

In This Thread

Prev Next