October 2010 - macruby-tickets - lists.macosforge.org

[MacRuby] #967: Boolean pointer creation assertion
by MacRuby 25 Oct '10

25 Oct '10

#967: Boolean pointer creation assertion -------------------------------------+-------------------------------------- Reporter: mattaimonetti@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- When trying to create a pointer to a boolean using this syntax: {{{ Pointer.new(:boolean) }}} MacRuby isn't happy: {{{ Assertion failed: (size > 0), function convert_type, file compiler.cpp, line 5808. Abort trap }}} However, using the alternative syntax: {{{ Pointer.new_with_type(:B) }}} just works fine. -- Ticket URL: <http://www.macruby.org/trac/ticket/967> MacRuby <http://macruby.org/>

1 2

[MacRuby] #963: Need to implement rb_iterate
by MacRuby 25 Oct '10

25 Oct '10

#963: Need to implement rb_iterate ---------------------------------------+------------------------------------ Reporter: joshua.ballanco@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.8 Component: MacRuby | Keywords: ---------------------------------------+------------------------------------ MacRuby claims to implement rb_iterate, but it does not. This causes problems with gherkin: {{{ dyld: Symbol not found: _rb_iterate Referenced from: /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/gherkin-2.2.9/lib/gherkin_lexer_en.bundle Expected in: flat namespace }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/963> MacRuby <http://macruby.org/>

1 1

[MacRuby] #964: Need to implement rb_global_variable
by MacRuby 24 Oct '10

24 Oct '10

#964: Need to implement rb_global_variable ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- {{{ $ macruby hpricot.rb dyld: lazy symbol binding failed: Symbol not found: _rb_global_variable Referenced from: /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/hpricot-0.8.2/lib/fast_xs.bundle Expected in: flat namespace dyld: Symbol not found: _rb_global_variable Referenced from: /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/hpricot-0.8.2/lib/fast_xs.bundle Expected in: flat namespace zsh: trace trap macruby hpricot.rb }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/964> MacRuby <http://macruby.org/>

1 1

[MacRuby] #962: Appscript framework causes EXC_BAD_ACCCESS error with MacRuby 0.7
by MacRuby 22 Oct '10

22 Oct '10

#962: Appscript framework causes EXC_BAD_ACCCESS error with MacRuby 0.7 --------------------------------------+------------------------------------- Reporter: gabriel.gilder@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: appscript --------------------------------------+------------------------------------- Setup: 1. Build the Appscript framework from https://appscript.svn.sourceforge.net/svnroot/appscript/objc- appscript/trunk 2. Install the framework in /Library/Frameworks or ~/Library/Frameworks 3. Checkout macruby-appscript from https://appscript.svn.sourceforge.net/svnroot/appscript/macruby- appscript/trunk 4. cd to trunk and run `sudo macruby setup.rb` Steps to reproduce: 1. Start a new MacRuby Application project 2. Add the Appscript.framework to Frameworks 3. Add "require 'appscript'" to rb_main.rb 4. Build and run In MacRuby 0.7, the resulting error occurs: [Switching to process 39091] Running… Program received signal: “EXC_BAD_ACCESS”. sharedlibrary apply-load-rules all warning: Unable to restore previously selected frame. Data Formatters temporarily unavailable, will re-try after a 'continue'. (Not safe to call dlopen at this time.) And the debugger opens up with some kind of memory trace that makes no sense to me. :) It runs perfectly with MacRuby 0.6. Please let me know if I can provide any more information... thanks! -Gabriel -- Ticket URL: <http://www.macruby.org/trac/ticket/962> MacRuby <http://macruby.org/>

1 4

[MacRuby] #895: MacRuby crashes when trying to parse an XML document with nokogiri
by MacRuby 20 Oct '10

20 Oct '10

#895: MacRuby crashes when trying to parse an XML document with nokogiri ---------------------------+------------------------------------------------ Reporter: haxie1@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ---------------------------+------------------------------------------------ Trying to parse an xml document with Nokogiri and MacRuby 0.7. The following crashes MacRuby. {{{ require 'rubygems' require 'nokogiri' xmlFile = File.open(File.expand_path(path), "r") xml = Nokogiri::XML(xmlFile) #crash }}} Here is the crash report attached. -- Ticket URL: <http://www.macruby.org/trac/ticket/895> MacRuby <http://macruby.org/>

1 5

[MacRuby] #961: MacRuby trunk doesn't show the correct file and line numbers in stacktraces involving blocks
by MacRuby 20 Oct '10

20 Oct '10

#961: MacRuby trunk doesn't show the correct file and line numbers in stacktraces involving blocks --------------------------------+------------------------------------------- Reporter: manfred@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: --------------------------------+------------------------------------------- Running the following code in MacRuby: {{{ require 'rubygems' require 'bacon' Bacon.extend Bacon::TestUnitOutput Bacon.summary_on_exit describe "Something" do it "fails" do raise 'foo' end end }}} shows the following stacktrace: {{{ lsof% macruby t.rb E RuntimeError: foo /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/ruby/Gems/1.9.2/gems/bacon-1.1.0/lib/bacon.rb:in `handle_requirement:': Something - fails /Users/manfred/Code/t.rb:8:in `block' /Users/manfred/Code/t.rb:7:in `<main>' 1 tests, 0 assertions, 0 failures, 1 errors }}} Ruby 1.9.2 shows line numbers and the fact that the code is run from a block in it's stacktrace, which is a lot more informative: {{{ lsof% /opt/ruby-1.9.2/bin/ruby t.rb E RuntimeError: foo t.rb:9:in `block (2 levels) in <main>': Something - fails t.rb:8:in `block in <main>' t.rb:7:in `<main>' 1 tests, 0 assertions, 0 failures, 1 errors }}} This means that you can only identify the top level block in which the error occurred, which is usually not enough because it's basically the complete testcase. -- Ticket URL: <http://www.macruby.org/trac/ticket/961> MacRuby <http://macruby.org/>

1 2

Re: [MacRuby] #594: Not all methods visible to objective-c calls
by MacRuby 19 Oct '10

19 Oct '10

#594: Not all methods visible to objective-c calls ------------------------------+--------------------------------------------- Reporter: michael@… | Owner: lsansonetti@… Type: defect | Status: new Priority: critical | Milestone: Component: MacRuby | Keywords: ------------------------------+--------------------------------------------- Comment(by mattaimonetti@…): Here is a blog post covering the problem and the work around: [http://merbist.com/2010/10/19/macruby-webkit-and-js/] Laurent says it's planning on getting that fixed in 0.8 -- Ticket URL: <http://www.macruby.org/trac/ticket/594#comment:6> MacRuby <http://macruby.org/>

1 0

[MacRuby] #950: no syntax for method calls with unnamed arguments after the pseudo-hash part of the selector
by MacRuby 19 Oct '10

19 Oct '10

#950: no syntax for method calls with unnamed arguments after the pseudo-hash part of the selector ---------------------------------+------------------------------------------ Reporter: dev@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ NSAlert defines the following method: {{{ + (NSAlert *)alertWithMessageText:(NSString *)messageTitle defaultButton:(NSString *)defaultButtonTitle alternateButton:(NSString *)alternateButtonTitle otherButton:(NSString *)otherButtonTitle informativeTextWithFormat:(NSString *)informativeText, ... }}} (http://bit.ly/d1JIeQ) Now, the interesting part here is the "`, ...`" at the end. It takes variable arguments at the end that work as formatting arguments for `informativeText`, eg.` sprintf(informativeText, ...)`. In MacRuby, this is currently invalid syntax: {{{ NSAlert.alertWithMessageText("Delete?", defaultButton:"Delete", alternateButton:"Cancel", otherButton:nil, informativeTextWithFormat:"delete %d people?", employees.count) }}} The only way around it is using `send`: {{{ NSAlert.send( :"alertWithMessageText:defaultButton:alternateButton:otherButton:informativeTextWithFormat:", "Delete?", "Delete", "Cancel", nil, "delete %@ people?", employees.count) }}} Mailing list thread: http://lists.macosforge.org/pipermail/macruby- devel/2010-October/006179.html -- Ticket URL: <http://www.macruby.org/trac/ticket/950> MacRuby <http://macruby.org/>

1 2

[MacRuby] #957: [Macruby sharedRuntime] should relocate paths when embedded in a Objective-C app
by MacRuby 19 Oct '10

19 Oct '10

#957: [Macruby sharedRuntime] should relocate paths when embedded in a Objective-C app ----------------------------------+----------------------------------------- Reporter: martinkahr@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- When the Macruby framework is embedded in an objective-c app, than the paths to the ruby libs and scripts are not set correct. I got the following info from Laurent: "When you work with a pure MacRuby Xcode project, which calls macruby_main(), MacRuby will automatically relocate the paths for you if it's embedded inside the running .app" The same thing should be done when an app is talking with MacRuby through [MacRuby sharedRuntime]. You can circumvent this problem by setting the paths by yourself. To see which paths must be set, you should check the output of macruby -e 'p $:' (Thanks to Laurent for the info) -- Ticket URL: <http://www.macruby.org/trac/ticket/957> MacRuby <http://macruby.org/>

1 1

[MacRuby] #959: CALayers can have a problem resolving method in superclass.
by MacRuby 19 Oct '10

19 Oct '10

#959: CALayers can have a problem resolving method in superclass. -------------------------------------+-------------------------------------- Reporter: eloy.de.enige@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: 0.8 -------------------------------------+-------------------------------------- 1. Run: macruby super_reduction.rb 2. Bring window to front 3. Close window 4. Poof, it raises a NoMethodError However, it should not raise, the method it should work. In the script are some comments about what combinations do work etc. It seems to be that using the same method name for two different lineages of classes (in combination with notifications) make the dispatcher go nuts, but this is just my gut feeling. -- Ticket URL: <http://www.macruby.org/trac/ticket/959> MacRuby <http://macruby.org/>

1 2