March 2012 - macruby-tickets - lists.macosforge.org

[MacRuby] #1471: '0.0 % 0.0' should not raise exception, but should return NaN.
by MacRuby 15 May '12

15 May '12

#1471: '0.0 % 0.0' should not raise exception, but should return NaN. ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- {{{ $ ruby19 -e 'p 0.0 % 0.0' NaN $ macruby -e 'p 0.0 % 0.0' -e:1:in `%': divided by 0 (ZeroDivisionError) }}} Test Script: {{{ require 'test/unit/assertions.rb' include Test::Unit::Assertions assert_equal("NaN", (1.0 % 0.0).to_s) assert_raise(ZeroDivisionError){ 1.0.send(:%, 0.0) } assert_raise(ZeroDivisionError){ 1.0 % 0 } assert_raise(ZeroDivisionError){ 1.0.modulo(0.0) } }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/1471> MacRuby <http://macruby.org/>

1 1

[MacRuby] #1466: does not install MacRuby's Templetes and rb_nibtool into Xcode 4.3
by MacRuby 09 May '12

09 May '12

#1466: does not install MacRuby's Templetes and rb_nibtool into Xcode 4.3 ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: critical | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- MacRuby's Templates, tools and Examples are installed into "/Developer/xxxx".[[BR]] However, "/Developer" directory is not created by installing Xcode 4.3. So, I think that it needs to change the installation location. -- Ticket URL: <http://www.macruby.org/trac/ticket/1466> MacRuby <http://macruby.org/>

1 11

[MacRuby] #1429: STDIN.eof? consumes first input character
by MacRuby 17 Apr '12

17 Apr '12

#1429: STDIN.eof? consumes first input character --------------------------------+------------------------------------------- Reporter: lastobelus@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: --------------------------------+------------------------------------------- {{{ irb(main):045:0> def test irb(main):046:1> STDIN.eof? irb(main):047:1> STDIN.gets irb(main):048:0> end => nil irb(main):049:0> test bob => "ob\n" }}} - I checked File and StringIO, they do not show this bug. - I was unable to come up with a workaround that would work with client code calling STDIN.eof? then STDIN.gets. Any suggestions would be appreciated. I tried STDIN.reopen and STDIN.rewind -- Ticket URL: <http://www.macruby.org/trac/ticket/1429> MacRuby <http://macruby.org/>

1 2

[MacRuby] #1432: macruby fails with error "JSON::Ext::Generator::GeneratorMethods::Object:Class is not a module" while using cucumber 1.1.4
by MacRuby 13 Apr '12

13 Apr '12

#1432: macruby fails with error "JSON::Ext::Generator::GeneratorMethods::Object:Class is not a module" while using cucumber 1.1.4 ---------------------------------------+------------------------------------ Reporter: matthieu.desile@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ---------------------------------------+------------------------------------ Hello, I tried using cucumber with macruby and it fails to run with error "JSON::Ext::Generator::GeneratorMethods::Object:Class is not a module" I installed the latest (1.1.4) cucumber gem version and when I run it on a simple feature, it fails. Complete error message : $ macruby_select 0.12 -S cucumber simple.feature /Volumes/Users/furai/.gem/macruby/1.9.2/gems/cucumber-1.1.4/lib/cucumber.rb:10:in `<main>': JSON::Ext::Generator::GeneratorMethods::Object:Class is not a module (TypeError) from /Volumes/Users/furai/.gem/macruby/1.9.2/gems/cucumber-1.1.4/bin/cucumber:11:in `<main>' from /Volumes/Users/furai/.gem/macruby/1.9.2/bin/cucumber:19:in `<main>' It fails the same using macruby 0.9, 0.10, 0.11 and nightly build, it fails with cucumber version 1.0.0 to 1.1.4. -- Ticket URL: <http://www.macruby.org/trac/ticket/1432> MacRuby <http://macruby.org/>

1 3

[MacRuby] #1446: Add additional diagnostic info when assertion fails in RoxorVM::pop_current_exception
by MacRuby 04 Apr '12

04 Apr '12

#1446: Add additional diagnostic info when assertion fails in RoxorVM::pop_current_exception --------------------------------+------------------------------------------- Reporter: msabramo@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: --------------------------------+------------------------------------------- I've discovered that it's not difficult to make MacRuby crash by doing things that it doesn't like. For instance, right now I'm debugging this crash in my app: `Assertion failed: ((size_t)pos < current_exceptions.size()), function pop_current_exception, file vm.cpp, line 3596.` From a little big of digging around, I gather that this is probably coming from in `RoxorVM::pop_current_exception` in https://github.com/MacRuby/MacRuby/blob/master/vm.cpp#L3600 I propose to add more information about `current_exceptions` when this assertion fails. I will work on this and submit a GitHub pull request... -- Ticket URL: <http://www.macruby.org/trac/ticket/1446> MacRuby <http://macruby.org/>

1 5

[MacRuby] #1492: Fails the Spec about the Range#relative_to
by MacRuby 31 Mar '12

31 Mar '12

#1492: Fails the Spec about the Range#relative_to ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- Latest MacRuby fails the Spec about the Range#relative_to {{{ $ rake spec:ci rm -rf rubyspec_temp ./mspec/bin/mspec ci -B ./spec/macruby.mspec :full ---- snip --- 1) A Range object responds to #relative_to, which returns a new Range object without negative indicies FAILED Expected 0..11 to equal 0..10 /Users/watson/src/macruby-master/spec/macruby/core/range_spec.rb:14:in `block' /Users/watson/src/macruby-master/spec/macruby/core/range_spec.rb:1:in `<main>' Finished in 277.238063 seconds 3368 files, 15915 examples, 59178 expectations, 1 failure, 0 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/macruby.msp...] Tasks: TOP => spec:ci (See full trace by running task with --trace) }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/1492> MacRuby <http://macruby.org/>

1 3

[MacRuby] #1491: Dispatch::Source.timer should not repeat if specify TIME_FOREVER to interval.
by MacRuby 31 Mar '12

31 Mar '12

#1491: Dispatch::Source.timer should not repeat if specify TIME_FOREVER to interval. ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- Test Script: {{{ gcdq = Dispatch::Queue.new('sample') timer = Dispatch::Source.timer(1, Dispatch::TIME_FOREVER, 0, gcdq) do |s| puts "Wake up!" end sleep 3 }}} Result: {{{ $ macruby gcd.rb Wake up! Wake up! Wake up! Wake up! ---- snip ---- }}} I wrote same code with Objective-C, and it does not repeat. {{{ #import <Foundation/Foundation.h> int main(void) { NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; dispatch_queue_t queue = dispatch_queue_create("sample", NULL); dispatch_source_t timer = dispatch_source_create(DISPATCH_SOURCE_TYPE_TIMER, 0, 0, queue); dispatch_source_set_timer(timer, dispatch_time(DISPATCH_TIME_NOW, 1ull * NSEC_PER_SEC), DISPATCH_TIME_FOREVER, 0); dispatch_source_set_event_handler(timer, ^{ NSLog(@"Wake up"); }); dispatch_resume(timer); sleep(3); [pool release]; return 0; } }}} {{{ $ gcc gcd.m -framework Foundation $ ./a.out 2012-03-31 09:33:59.188 a.out[61445:1703] Wake up $ }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/1491> MacRuby <http://macruby.org/>

1 1

[MacRuby] #1490: should define constants of "MACH_SEND" and "MACH_RECV" in Dispatch::Source.
by MacRuby 31 Mar '12

31 Mar '12

#1490: should define constants of "MACH_SEND" and "MACH_RECV" in Dispatch::Source. ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- SOURCE_TYPE_MACH_SEND and SOURCE_TYPE_MACH_RECV are enumerated in https://github.com/MacRuby/MacRuby/blob/master/gcd.c#L54-55 However, they does not used by definition of constants in https://github.com/MacRuby/MacRuby/blob/master/gcd.c#L1419 I hope to define Dispatch::Source::MACH_SEND and Dispatch::Source::MACH_RECV -- Ticket URL: <http://www.macruby.org/trac/ticket/1490> MacRuby <http://macruby.org/>

1 2

[MacRuby] #1475: The Dispatch::Group#notify docs are incorrect.
by MacRuby 30 Mar '12

30 Mar '12

#1475: The Dispatch::Group#notify docs are incorrect. -------------------------------------+-------------------------------------- Reporter: eloy.de.enige@… | Owner: eloy.de.enige@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- The documentation does not show the Queue instance that has to be specified. https://github.com/MacRuby/MacRuby/blob/master/gcd.c#L769 -- Ticket URL: <http://www.macruby.org/trac/ticket/1475> MacRuby <http://macruby.org/>

1 1

[MacRuby] #1477: Macirb no longer understands blocks with more than one argument
by MacRuby 29 Mar '12

29 Mar '12

#1477: Macirb no longer understands blocks with more than one argument --------------------------------+------------------------------------------- Reporter: lastobelus@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: --------------------------------+------------------------------------------- Since the Jan. 12th nightly, macirb no longer understands blocks with more than one argument: {{{ irb(main):002:0> h={:a => "a", :b => "b"} => {:a=>"a", :b=>"b"} irb(main):003:0> h.each{|k,v| puts k;puts v} SyntaxError: compile error (irb):3: duplicated argument name }}} (In the first few builds after jan 12, this caused a breakpoint trap) -- Ticket URL: <http://www.macruby.org/trac/ticket/1477> MacRuby <http://macruby.org/>

1 2