January 2010 - MacRuby-devel - lists.macosforge.org

[MacRuby] #308: "too short multibyte code string" when using Pathname
by MacRuby 25 Mar '10

25 Mar '10

#308: "too short multibyte code string" when using Pathname -------------------------------+-------------------------------------------- Reporter: tjw@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------+-------------------------------------------- Possibly related, but simpler case of https://www.macruby.org/trac/ticket/303 See the attached script, which hits a regex parse error when run. Digging around, it looks like this might start from lib/pathname.rb in #initialize: if /\0/ =~ @path raise ArgumentError, "pathname contains \\0: #{(a)path.inspect}" end The /\0/ fails to parse and a RegexpError error is thrown. -- Ticket URL: <http://www.macruby.org/trac/ticket/308> MacRuby <http://macruby.org/>

1 2

[MacRuby] #179: Calling Regexp#match from ObjC in a background thread hangs
by MacRuby 25 Mar '10

25 Mar '10

#179: Calling Regexp#match from ObjC in a background thread hangs -------------------------------+-------------------------------------------- Reporter: tjw@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------+-------------------------------------------- Calling this from a foreground thread works fine, but if I call Regexp#match from ObjC in a background thread, it hangs. Attaching example. -- Ticket URL: <http://www.macruby.org/trac/ticket/179> MacRuby <http://macruby.org/>

1 1

[MacRuby] #244: String.name should return "String" and not "NSMutableString"
by MacRuby 25 Mar '10

25 Mar '10

#244: String.name should return "String" and not "NSMutableString" -------------------------------+-------------------------------------------- Reporter: carllerche@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------+-------------------------------------------- macirb >> String.name # => "NSMutableString" I believe that it is a ruby expectation that core classes will have the same name on any ruby implementation. Extlib and other libraries rely on this fact. -- Ticket URL: <http://www.macruby.org/trac/ticket/244> MacRuby <http://macruby.org/>

1 3

[MacRuby] #529: Using a Proc as a ‘callback function’
by MacRuby 23 Mar '10

23 Mar '10

#529: Using a Proc as a ‘callback function’ -------------------------------------+-------------------------------------- Reporter: eloy.de.enige@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- Some Cocoa methods, or C functions, take pointers to functions which can be used as callbacks. For instance, FSEventStreamCreate: http://bit.ly/8p70Yw. RubyCocoa, in conjunction with BridgeSupport, supported this by allowing the user to give a proc that would be used as the callback. MacRuby should support this too. Here's a spec example: {{{ describe "BridgeSupport" do it "bridges a proc to be used where a pointer to a callback function is required" do array = [5, 3, 2, 4, 1] proc = Proc.new do |x, y, context_pointer| context = context_pointer[0].chr + context_pointer[1].chr + context_pointer[2].chr x <=> y if context == 'foo' end array.sortUsingFunction(proc, context: 'bar') array.should == [5, 3, 2, 4, 1] array.sortUsingFunction(proc, context: 'foo') array.should == [1, 2, 3, 4, 5] end end }}} Don't know if this is feasible, but it would be great if the arguments given to the proc, like the context argument, were no Pointer objects, but the object they actually point to: {{{ describe "BridgeSupport" do it "bridges a proc to be used where a pointer to a callback function is required" do array = [5, 3, 2, 4, 1] proc = Proc.new do |x, y, context| x <=> y if context == 'foo' end array.sortUsingFunction(proc, context: 'bar') array.should == [5, 3, 2, 4, 1] array.sortUsingFunction(proc, context: 'foo') array.should == [1, 2, 3, 4, 5] end end }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/529> MacRuby <http://macruby.org/>

1 5

[MacRuby] #509: Beta 0.5 does not allow methods with more than 11 arguments
by MacRuby 26 Feb '10

26 Feb '10

#509: Beta 0.5 does not allow methods with more than 11 arguments -----------------------------------+---------------------------------------- Reporter: johnmacshea@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: -----------------------------------+---------------------------------------- With methods with more than 11 arguments MacRuby beta 0.5 crashes. Eg with 12 arguments: invalid argc 12 Abort trap BTW: this was not the case with 0.4 (I assume it is not a Ruby 1.9.x issue?) -- Ticket URL: <http://www.macruby.org/trac/ticket/509> MacRuby <http://macruby.org/>

1 3

[MacRuby] #423: #respond_to? returns true, actual method call raises NoMethodError
by MacRuby 23 Feb '10

23 Feb '10

#423: #respond_to? returns true, actual method call raises NoMethodError ---------------------------------+------------------------------------------ Reporter: ecin@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ framework 'Cocoa' a = NSMetadataQuery.new a.respond_to? :setPredicate # => true a.setPredicate # => NoMethodError: undefined method `setPredicate' for #<NSMetadataQuery:0x2002a1e20> a.setPredicate "a" # => RuntimeError: NSInvalidArgumentException: -[NSCFString generateMetadataDescription]: unrecognized selector sent to instance 0x2002309c0 -- Ticket URL: <http://www.macruby.org/trac/ticket/423> MacRuby <http://macruby.org/>

1 5

[MacRuby] #512: MacRuby misreports #initialize argument count in error messages
by MacRuby 23 Feb '10

23 Feb '10

#512: MacRuby misreports #initialize argument count in error messages -----------------------------------+---------------------------------------- Reporter: matthew@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: -----------------------------------+---------------------------------------- Given the following code, {{{ class A def initialize(a, b, c) end end A.new }}} '''Expected result (Ruby 1.9.1)''' {{{ArgumentError: wrong number of arguments (0 for 3)}}} '''Actual result (MacRuby 0.5b2)''' {{{ArgumentError: wrong number of arguments (0 for 1)}}} -- Ticket URL: <http://www.macruby.org/trac/ticket/512> MacRuby <http://macruby.org/>

1 2

[MacRuby] #555: Redefinition of method gives unexpected behavior
by MacRuby 18 Feb '10

18 Feb '10

#555: Redefinition of method gives unexpected behavior --------------------------------+------------------------------------------- Reporter: maccheck@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: --------------------------------+------------------------------------------- When I run following test program with Ruby 1.9.1/1.8.7 and MacRuby 0.5b2 I get an unexpected result: {{{ class TestClass def initialize; @a_var = "content"; end end a = TestClass.new; puts "a: %s" % a.inspect class TestClass def initialize(k); @a_var = k; end end b = TestClass.new "valueGiven"; puts "b: %s" % b.inspect c = TestClass.new; puts "c: %s" % c.inspect }}} results in Ruby 1.9.1/1.8.7 with the expected behavior: {{{ a: #<TestClass:0x100155d50 @a_var="content"> b: #<TestClass:0x100155b20 @a_var="valueGiven"> initTest.rb:13:in `initialize': wrong number of arguments (0 for 1) (ArgumentError) from initTest.rb:13:in `new' from initTest.rb:13 }}} In MacRuby I get following output: {{{ a: ##-<TestClass:0x200020b60 @a_var="content"> b: ##-<TestClass:0x2000213e0 @a_var="valueGiven"> c: ##-<TestClass:0x200021820 @a_var="content"> }}} It seems that {{{#initialize}}} (without arguments) is still floating around... -- Ticket URL: <http://www.macruby.org/trac/ticket/555> MacRuby <http://macruby.org/>

1 3

[MacRuby] #579: i386 compilation doesn't work
by MacRuby 15 Feb '10

15 Feb '10

#579: i386 compilation doesn't work --------------------------------+------------------------------------------- Reporter: carlo@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: --------------------------------+------------------------------------------- This bug report references MR0.5b2 as well as its standard MacRuby application template. Trying to build self-contained compiled i386 apps (embedded MR) works fine, but the apps won't run. i86_64 builds are showing no problems and work as expected, but i386 versions exit right away, logging the following error message: {{{ core:in `each': no such file to load -- bootstrap (LoadError) from [project path]/build/Release/MyApp.app/Contents/Resources/rb_main.rb:in `<main>' }}} "bootstrap" being whatever *.rbo file is to be loaded first. $LOAD_PATH looks okay, i.e. it's identical when running i386 or x86_64 code. The behaviour is the same on both single-arch builds and 32/64bit "combo" builds. Not compiling the the application yields an app which works a-okay on both architectures. Tried on a 2006 2GHz Core Duo MacBook as well as a late 2009 C2D iMac, both running XCode 3.2.1 on 10.6.2. (Both being *my* machines makes it possible I've somehow managed to misconfigure them in the same way, of course.) -- Ticket URL: <http://www.macruby.org/trac/ticket/579> MacRuby <http://macruby.org/>

1 8

[MacRuby] #284: [HotCocoa] start of NSUserDefaults mapping
by MacRuby 12 Feb '10

12 Feb '10

#284: [HotCocoa] start of NSUserDefaults mapping ---------------------------------+------------------------------------------ Reporter: dj2@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ Attached is the start of a mapping for NSUserDefaults. This adds in a [], []= and delete methods for accessing the options. -- Ticket URL: <http://www.macruby.org/trac/ticket/284> MacRuby <http://macruby.org/>

1 1