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

Re: [MacRuby-devel] MacRuby-devel Digest, Vol 34, Issue 9
by Vegar Vikan 03 Dec '10

03 Dec '10

Hi, Yes, I didn't see that before I posted here. I have downloaded the nightly build, and managed to compile a simple 'hello-world' application. Look forward to check it out some more after the weekend. Both MacRuby and Sequel excites me. Thanks, -Vegar Den 3. des. 2010 kl. 16:00 skrev macruby-devel-request(a)lists.macosforge.org: > Hi Vegar, as Laurent said on your stackoverflow ticket, sequel works out-of-the-box on MacRuby trunk (and nightly): $ /usr/local/bin/macruby -r rubygems -e "require 'sequel'; p 42" 42 Eloy On Fri, Dec 3, 2010 at 10:16 AM, Vegar Vikan <vegar(a)vi-kan.net> wrote: Hi, Someone says Sequel is possible to use with MacRuby, someone says its not... When I try, I get an error message, which I have posted on StackOverflow (http://stackoverflow.com/questions/4339601/macruby-error-when-using-sequel) One of the answers suggest that I cross-post the question to this mailing list, so now I do... Regards, -Vegar _______________________________________________ MacRuby-devel mailing list MacRuby-devel(a)lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

1 0

MacRuby and Sequel
by Vegar Vikan 03 Dec '10

03 Dec '10

Hi, Someone says Sequel is possible to use with MacRuby, someone says its not... When I try, I get an error message, which I have posted on StackOverflow (http://stackoverflow.com/questions/4339601/macruby-error-when-using-sequel) One of the answers suggest that I cross-post the question to this mailing list, so now I do... Regards, -Vegar

2 1

Regular expression related performance
by Yasu Imao 03 Dec '10

03 Dec '10

Hello, I'm rewriting an app for text analysis in MacRuby, which I originally wrote in RubyCocoa. But I encountered a serious performance issue in MacRuby, which is related to processing text using regular expressions. I'm wondering if this will be taken care of in the near future (or already done in 0.8?). Below are my simple tests. The first two are essentially the same with a slightly different approach. Both are simply counting frequency of each word. I want to use the first approach not to count word frequencies, but in other processes. The third one is to test the speed of String#gsub with regular expression. I felt String#gsub was slow in my app, so I just wanted to test how slow it is compared to RubyCocoa. Test 1 - scan-block freq = Hash.new(0) text.scan(/\w+/) do |word| freq[word] += 1 end Test 2 - scan array.each freq = Hash.new(0) text.scan(/\w+/).each do |word| freq[word] += 1 end Test 3 - gsub upcase text.gsub!(/\w+/){|x| x.upcase} The results are in seconds. The original text is in English with 8154 words. Each process was repeated 10 times to calculate processing times. Each test were done 3 times. Ruby 1.8.7 Test1 - scan-block: 0.542, 0.502, 0.518 Ruby 1.8.7 Test2 - scan array.each: 0.399, 0.392, 0.399 Ruby 1.8.7 Test3 - gsub upcase: 0.384, 0.349, 0.390 MacRuby 0.7.1 Test1 - scan-block: 27.612, 27.707, 27.453 MacRuby 0.7.1 Test2 - scan array.each: 3.556, 3.616, 3.554 MacRuby 0.7.1 Test3 - gsub upcase: 27.613, 26.826, 27.327 Thanks, Yasu

6 16

Getting a pointer to a boxed type
by Mark Rada 02 Dec '10

02 Dec '10

Hi, With the recent closing of ticket #1002 I have been trying to take a bunch of Objective-C code and write it in MacRuby. One problem that I have run into is with the AXValueGetValue() function in AXValue.h. The last argument to the function is supposed to be the address of a structure to populate; a fragment of that code would look like this: AXValueRef value = (AXValueRef)[self valueOfAttribute:attribute]; CGPoint point; AXValueGetValue( value, kAXValueCGPointType, &point ); return point; If I wanted to write this in MacRuby I think I would have to do something like this: value = valueOfAttribute attribute point = CGPoint.new AXValueGetValue( value, KAXValueCGPointType, point.address_of ) point Except that I have not come across a way to get the address of an object in MacRuby. I have tried the #object_id but then I get errors about the function wanting a Pointer. Is there a way to get a pointer to a specific object or a way to get the address of an object? Thanks, Mark

2 2

Compile target
by Robert Rice 02 Dec '10

02 Dec '10

Hi MacRuby devotees: Would it be possible to configure XCODE and macruby_deploy to produce the compiled output in a separate folder and not delete the .rb source files? The .rbo files should be given the same time stamp as the .rb file so that recompiling could be optimized to only the files that have changed since the last compile. Thanks, Bob Rice

2 1

converging for 1.0
by Laurent Sansonetti 01 Dec '10

01 Dec '10

Hi guys, Now that the vacations are behind us (well, behind me at least :)), it's time to focus on converging MacRuby for its first stable release, 1.0. My goal is to release it somewhere in 2011 (the sooner the better :)). In order to smoothly achieve that goal, it's also time to accelerate the current release system and improve the way we classify and address incoming bugs reports. After talking with the others committers we decided on the following: 1) Much more frequent releases Starting from now we will release more frequently. Until we reach 1.0, releases will mostly contain bug fixes and improvements, and practically no feature. As a matter of fact, I intend to release trunk as 0.8 next week. By releasing MacRuby more frequently we hope people will also test MacRuby more frequently, and report more bugs. 2) Better bug management We have too many bugs registered in the tracker, and it's a pain to manage all of them. Starting from now, we will classify all existing bugs as well as incoming ones in two categories: for 1.0 and for later. We will then only focus on bugs for 1.0. The second step is to reduce the problem into a small test case (if applicable) then attach the #reduction keyword. Once bugs are properly reduced, we can fix them more easily. We intend to attach a keyword to bugs that seem to be easy to fix, this way new comers can help and learn how MacRuby works. 3) Bug smash days We will organize bug smash days. They will happen on an IRC channel (details forthcoming). The first one will happen this saturday, 6th December. We will have people from 3 different time zones (US west coast, Europe and Japan) on the IRC channel, and our first task will be to start managing all the bugs, using the method described above. New comers are greatly welcomed and we will make sure everyone who wants to help can help. 4) Compatibility support page The big challenge for MacRuby 1.0 is to have excellent Ruby compatibility. We currently have 2 metrics to test our Ruby compatibility: RubySpec and Rails. However it's not enough, there are lots of Ruby libraries and C extensions around that we can't afford to test by ourselves. Therefore, we intend to prepare a webpage on the website that lists Ruby libraries that are known to work with MacRuby, and those who don't run yet. We will make sure the community can easily update that page. Having an updated list of libraries that we should run should help the team fixing compatibility bugs. That's all for now, bug if you have any suggestion on how to improve the current development process, please let us know. Laurent

11 13