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

PostgreSQL (was: Re: [ANN] MacRuby 0.6)
by Tiago Ribeiro 04 May '10

04 May '10

More specifically, I've been getting the following problem when trying to install the PostgreSQL extension, so I was wondering if there's anything else that has to be done: imac:~ tiagor$ sudo macgem install postgres Building native extensions. This could take a while... ERROR: Error installing postgres: extconf failed: /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/bin/macruby extconf.rb /Library/Frameworks/MacRuby.framework/Versions/0.6/usr/lib/ruby/Gems/1.9.0/gems/postgres-0.7.9.2008.01.28/ext/extconf.rb:70:in `<main>': uninitialized constant PLATFORM (NameError) imac:~ tiagor$ Any idea? On Tuesday, May 04, 2010, at 05:06PM, "Tiago Ribeiro" <tiagor(a)mac.com> wrote: > Amazing. > >I'm mostly amazed by this specific breakthrough: > >"MacRuby 0.6 provides support for C extensions written for the original implementation of ruby. We were able to successfully use the Nokogiri, SQLite3 and PostgreSQL extensions from MacRuby." > >How did you manage to install the PostgreSQL extension with macgem? Any special setup? > >Thanks a lot

1 0

[MacRuby] #677: Macruby segfaults when performing symbol#to_json
by MacRuby 04 May '10

04 May '10

#677: Macruby segfaults when performing symbol#to_json ----------------------------------+----------------------------------------- Reporter: bricollins@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- For example: {{{ require 'json' :macruby.to_json }}} I have attached a patch and test case, I also seem to be getting this issue with ruby 1.9.1 so maybe this patch could be applied there too. -- Ticket URL: <http://www.macruby.org/trac/ticket/677> MacRuby <http://macruby.org/>

1 1

[MacRuby] #674: Shoulda fails because of oddity with block_given?
by MacRuby 04 May '10

04 May '10

#674: Shoulda fails because of oddity with block_given? ---------------------------------+------------------------------------------ Reporter: marick@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ The attached file shows that shoulda (on 0.5 and a recent version of 0.7) behaves incorrectly. The important part is this: {{{ should "test something" do puts "I should be printed" end }}} The correct output shows that a test has been run: {{{ 1274 $ ruby shoulda-problem.rb ... I should be printed }}} With Macruby, you get this: {{{ 1275 $ macruby shoulda-problem.rb * DEFERRED: Samples should test something. }}} The problem is in this code: {{{ def should(name, options = {}, &blk) if Shoulda.current_context block_given? ? Shoulda.current_context.should(name, options, &blk) : Shoulda.current_context.should_eventually(name) else context_name = self.name.gsub(/Test/, "") context = Shoulda::Context.new(context_name, self) do ==> block_given? ? should(name, options, &blk) : should_eventually(name) end context.build end end }}} In Ruby 1.8.6 (and 1.9, I suppose, because Shoulda is said to work on 1.9), the block_given? inside a block given to an initializer is supposed to evaluate to true. (!!!) In Macruby, it evaluates to False. This problem is easy to patch (and I'd be inclined to think the Shoulda people should, given that the code is tricksy). Still, it is a deviation from reference Ruby behavior. -- Ticket URL: <http://www.macruby.org/trac/ticket/674> MacRuby <http://macruby.org/>

1 5

[ANN] MacRuby 0.6
by Laurent Sansonetti 04 May '10

04 May '10

Hi, After 3 months of development since the last release, MacRuby 0.6 is now available. Get it here while it's still hot! MacRuby is an implementation of Ruby 1.9 directly on top of Mac OS X core technologies such as the Objective-C runtime and garbage collector, the LLVM compiler infrastructure and the Foundation and ICU frameworks. It is the goal of MacRuby to enable the creation of full-fledged Mac OS X applications which do not sacrifice performance in order to enjoy the benefits of using Ruby. You can learn more about MacRuby, and download a binary installer, from the website: http://macruby.org Or about this release more specifically, on our blog: http://www.macruby.org/blog/2010/04/30/macruby06.html Enjoy, Laurent

6 9

Mocking package for 0.5+?
by Brian Marick 04 May '10

04 May '10

I've been looking for a combination of unit testing and mocking packages for macruby. (The mocking is the real problem.) If anyone does TDD with mocks: what do you use? ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant Author of /Programming Cocoa with Ruby/ www.exampler.com, www.exampler.com/blog, www.twitter.com/marick

1 1

[MacRuby] #683: rake failed for MacRuby-0.6 on Mac OS X 10.5.8
by MacRuby 04 May '10

04 May '10

#683: rake failed for MacRuby-0.6 on Mac OS X 10.5.8 ------------------------------+--------------------------------------------- Reporter: bhuelbue@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.6 Component: MacRuby | Keywords: rake ------------------------------+--------------------------------------------- Used ruby is bruno-huelbueschs-imac:MacRuby-0.6 bhuelbue$ ruby -v ruby 1.9.1p376 (2009-12-07 revision 26041) [i386-darwin9.8.0] Used rake is bruno-huelbueschs-imac:MacRuby-0.6 bhuelbue$ rake --version rake, version 0.8.7 see attached file. -- Ticket URL: <http://www.macruby.org/trac/ticket/683> MacRuby <http://macruby.org/>

1 0

Kernel#caller doesn't show directories
by Brian Marick 04 May '10

04 May '10

Suppose you have foo.rb: def __DIR__ caller[0] raise 'death' end puts __DIR__ If you call that from, say, a directory two levels below it, you get this: 818 $ macruby ../../foo.rb foo.rb:2:in `__DIR__': death (RuntimeError) from foo.rb:6:in `<main>' In 1.8.6 (and I sure hope in stock 1.9), you get filenames with the relative directory: 819 $ ruby ../../foo.rb ../../foo.rb:3:in `__DIR__': death (RuntimeError) from ../../foo.rb:6 I think that's important because there are tools (IDEs, my emacs hacks) that use the backtrace from a test to jump to the failing code. You can't do that unless you have the full pathname. I will file a ticket if this is a real bug. ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant Author of /Programming Cocoa with Ruby/ www.exampler.com, www.exampler.com/blog, www.twitter.com/marick

2 4

[MacRuby] #675: Trying to do I/O on empty NSString crashes MacRuby
by MacRuby 03 May '10

03 May '10

#675: Trying to do I/O on empty NSString crashes MacRuby ---------------------------+------------------------------------------------ Reporter: jkh@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.6 Component: MacRuby | Keywords: ---------------------------+------------------------------------------------ Easily demonstrated through Laurent's reduced example: % ./miniruby -e "puts NSString.string" Assertion failed: (max > 0), function rb_str_bstr, file string.c, line 5603. Abort trap: 6 -- Ticket URL: <http://www.macruby.org/trac/ticket/675> MacRuby <http://macruby.org/>

1 1

Debugging MacRuby
by Alexander von Below 03 May '10

03 May '10

Hello, we have grown fond of MacRuby, but found a few things that appear to be bugs. Our idea was, to install a symbolicated framework of MacRuby, to see what is going on in the guts. Surely this is possible, but is there a good "best practice" to building such a debug version? Thanks Alex

2 1

files delivered in site_ruby
by Brian Marick 03 May '10

03 May '10

MacRuby 0.7: There are files delivered in site_ruby: bigdecimal/ openssl/ ripper.rb digest/ openssl.rb universal-darwin10.0/ digest.rb ripper/ Shouldn't they be in vendor_ruby? I can't run a program without site-specific files by stripping site_ruby out of the path. If I do, macruby crashes with an Abort trap (in 0.5, at least) when it tries to load gems. I know that macruby_deploy -embed copies site_ruby into the application, so this causes no real problem other than wasted space, so maybe it's not worth fixing. But it'll cause more problems when macruby ships with OSX and people stop embedding. I'll file a ticket if needed. ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant Author of /Programming Cocoa with Ruby/ www.exampler.com, www.exampler.com/blog, www.twitter.com/marick

2 1