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

[MacRuby] #126: bytestrings, nsstring, and unicode/multibyte characters do not get along
by MacRuby 25 Mar '10

25 Mar '10

#126: bytestrings, nsstring, and unicode/multibyte characters do not get along -------------------------------------+-------------------------------------- Reporter: jordan.breeding(a)mac.com | Owner: lsansonetti(a)apple.com Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.4 Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- I will try to publish some example later, but I have seen problems trying to print bytestrings. Unicode has issues with "%s" so I tried using "%@" in most places. That worked until I tried using a bytestring, bytestrings don't get along with "%@". Most of this was outside of the bug tracker in emails with Laurent. -- Ticket URL: <http://www.macruby.org/trac/ticket/126> MacRuby <http://macruby.org/>

1 1

[MacRuby] #587: macgem fails with error
by MacRuby 25 Mar '10

25 Mar '10

#587: macgem fails with error ---------------------------+------------------------------------------------ Reporter: nexneo@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ---------------------------+------------------------------------------------ On 32bit MacBook macgem fails {{{ $ macgem list Password: /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/time.rb:351: too short escaped multibyte character: /\A\s* (?:Mon|Tue|Wed|Thu|Fri|Sat|Sun),\x20 (\d{2})\x20 (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)\x20 (\d{4})\x20 (\d{2}):(\d{2}):(\d{2})\x20 GMT \s*\z/ix /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/time.rb:358: too short escaped multibyte character: /\A\s* (?:Monday|Tuesday|Wednesday|Thursday|Friday|Saturday|Sunday),\x20 (\d\d)-(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)-(\d\d)\x20 (\d\d):(\d\d):(\d\d)\x20 GMT \s*\z/ix /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/time.rb:372: too short escaped multibyte character: /\A\s* (?:Mon|Tue|Wed|Thu|Fri|Sat|Sun)\x20 (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)\x20 (\d\d|\x20\d)\x20 (\d\d):(\d\d):(\d\d)\x20 (\d{4}) \s*\z/ix custom_require.rb:38:in `require:': compile error (SyntaxError) from remote_fetcher.rb:1:in `<main>' from custom_require.rb:38:in `require:' from spec_fetcher.rb:1:in `<main>' from custom_require.rb:38:in `require:' from query_command.rb:1:in `<main>' from custom_require.rb:38:in `require:' from list_command.rb:1:in `<main>' from custom_require.rb:38:in `require:' from command_manager.rb:129:in `load_and_instantiate:' }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/587> MacRuby <http://macruby.org/>

1 2

[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] #624: assigning a layout_view to a layout_view in a block and then assigning it to a window.view: fails
by MacRuby 10 Mar '10

10 Mar '10

#624: assigning a layout_view to a layout_view in a block and then assigning it to a window.view: fails ----------------------------------------+----------------------------------- Reporter: pontus.stromdahl@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: MacRuby 0.6 Component: MacRuby | Keywords: hotcocoa layout_view setFrame superclass ----------------------------------------+----------------------------------- I built MacRuby from the trunk and started a hotcocoa app that I've been working. I got this little thing: /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:321:in `setFrame:': super: no superclass method `setFrame' for #<HotCocoa::LayoutView:0x2005d32c0> (NoMethodError) So far I've tracked the problem to the following: if I do this, (assume that I have the code from the start method in the hotcocoa tutorial) win.view = layout_view do |view1| view1 << layout_view end then I get the error above. (see first trace below) if I do this instead win.view = layout_view view2 = layout_view win.view << view2 everything is well, except for some NSLock thing (see second trace below). This does not happen with 0.5. I used both the hotcocoa 0.5.1 gem as well as the current master from dj2. Running snow leopard on a macbook pro. pontus> macruby -v MacRuby version 0.6 (ruby 1.9.0) [universal-darwin10.0, x86_64] === First trace === pontus> macruby test.rb 2010-02-25 11:41:22.388 macruby[73985:903] *** -[NSLock unlock]: lock (<NSLock: 0x2000fea20> '(null)') unlocked when not locked 2010-02-25 11:41:22.391 macruby[73985:903] *** Break on _NSLockError() to debug. /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:321:in `setFrame:': super: no superclass method `setFrame' for #<HotCocoa::LayoutView:0x2005d32c0> (NoMethodError) from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:260:in `frame=:' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:372:in `block' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:364:in `relayout!' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:326:in `setFrameSize:' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/layout_view.rb:321:in `setFrame:' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/mappings/window.rb:71:in `view=:' from /Users/pontus/Workcopies/spike/macruby/setFrame_Fail/test.rb:9:in `block' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/mapper.rb:43:in `block' from /Users/pontus/Workcopies/spike/macruby/setFrame_Fail/test.rb:7:in `block' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/mappings/application.rb:8:in `handle_block:' from /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/hotcocoa-0.5.1.1/lib/hotcocoa/mapper.rb:43:in `block' from /Users/pontus/Workcopies/spike/macruby/setFrame_Fail/test.rb:1:in `<main>' pontus> macruby test.rb === Second trace === 2010-02-25 11:42:41.826 macruby[73989:903] *** -[NSLock unlock]: lock (<NSLock: 0x20053a340> '(null)') unlocked when not locked 2010-02-25 11:42:41.828 macruby[73989:903] *** Break on _NSLockError() to debug. -- Ticket URL: <http://www.macruby.org/trac/ticket/624> MacRuby <http://macruby.org/>

1 2

smaller macruby apps?
by Gary Weaver 26 Feb '10

26 Feb '10

In the MacRuby tutorial ( http://www.macruby.org/documentation/tutorial.html ) there is a brief section about Embedding MacRuby in Your Application, and when you use HotCocoa's macrake deploy, it includes the framework also. However, the smallest resulting app in MacRuby 0.5/HotCocoa 0.5.1 is roughly 150MB in size, which is much, much larger than the average small application on a Mac. Isaac Kearse noted a way to get around this in his post "Packaging A HotCocoa Application" ( http://isaac.kearse.co.nz/2010/02/01/packaging-hotcocoa/ ). I was just thinking, it would be nice if the same or similar method could be added to HotCocoa's deploy and/or possibly documented in the MacRuby tutorial as an alternative? Thanks! Gary

1 1

[MacRuby] #619: Constant scope in a block is determined at run-time?
by MacRuby 26 Feb '10

26 Feb '10

#619: Constant scope in a block is determined at run-time? --------------------------------+------------------------------------------- Reporter: chekenan@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: --------------------------------+------------------------------------------- r3572 Following code can't run by macruby. Both ruby 1.8.7 and 1.9.1 work. {{{ module A B = "Not defined in top-level." def self.extended(base) base.class_eval do puts B end end end class C # Not include A extend A end }}} NameError: uninitialized constant C::B from /Users/dche/(irb):6:in `block' from /Users/dche/(irb):5:in `extended:' -- Ticket URL: <http://www.macruby.org/trac/ticket/619> MacRuby <http://macruby.org/>

1 1

[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