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

iokit
by Joel Reymont 14 Feb '11

14 Feb '11

Has there been any progress with this ticket? http://www.macruby.org/trac/ticket/1126 Thanks, Joel -------------------------------------------------------------------------- - mac osx device driver ninja, kernel extensions and user-land usb drivers ---------------------+------------+--------------------------------------- http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont ---------------------+------------+---------------------------------------

1 0

MacRuby 0.9 - NSDate initWithTimeInterval:sinceDate: problem
by Jonathan Waddilove 14 Feb '11

14 Feb '11

Hi, I have been trying to use the NSDate initWithTimeInterval:sinceDate: method to measure elapsed times. I know there has been some discussion about the mapping from Cocoa NSDate to Ruby Time and back but I'm not sure if this is supposed to be working now? Here's a snip of code that calculates the interval using Ruby Time and then NSDate #!/usr/local/bin/macruby puts "Ruby Version: #{RUBY_VERSION}, MacRuby Version: #{MACRUBY_VERSION}" puts "\n\nRuby vesion - works as expected" point_in_time = Time.now puts "Ruby start time #{point_in_time}" sleep(1) later_time = Time.now puts "Later time: #{later_time}, interval: #{later_time - point_in_time} seconds" puts "\n\nFailing Cocoa version" cocoaTime = NSDate.date puts "Coca start time: #{cocoaTime}" sleep(1) cocoaFinishTime = NSDate.date puts "Cocoa Later time: #{cocoaFinishTime}, interval: #{cocoaFinishTime.timeIntervalSinceDate( cocoaFinishTime)} seconds" And here's the output, note the NSDate sees zero intervale... Ruby Version: 1.9.2, MacRuby Version: 0.8 Ruby vesion - works as expected Ruby start time 2011-02-13 16:33:23 +0000 Later time: 2011-02-13 16:33:24 +0000, interval: 1.000694 seconds Failing Cocoa version Coca start time: 2011-02-13 16:33:24 +0000 Cocoa Later time: 2011-02-13 16:33:25 +0000, interval: 0.0 seconds User error? or do I need to file a ticket? Best wishes and thanks, Jonathan

2 2

MacRuby 0.9 - crash using Proc.new with NSArray.enumerateObjectsUsingBlock
by Jonathan Waddilove 14 Feb '11

14 Feb '11

Hi, another MacRuby 0.9 question... I've been trying to use lambda and/or Proc.new to provide callback blocks (as suggested in Matt's excellent draft book). Again I have seen discussions about problems in this area and for me all the suggested variants of code fail. Here's a snip of failing code: #!/usr/local/bin/macruby puts "Ruby Version: #{RUBY_VERSION}, MacRuby Version: #{MACRUBY_VERSION}" a = [1, 2, 3, 4, 5,] a.enumerateObjectsUsingBlock(Proc.new {|obj, index, stop| puts "I'll bet this never displays" }) and here's the resulting crash... Any suggestions? many thanks, Jonathan Process: macruby [23078] Path: /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/bin/macruby Identifier: macruby Version: ??? (???) Code Type: X86-64 (Native) Parent Process: ruby [23074] Date/Time: 2011-02-13 16:50:33.806 +0000 OS Version: Mac OS X 10.6.6 (10J567) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: objc[23078]: garbage collection is ON Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 ??? 000000000000000000 0 + 0 1 ??? 0x0000000102d63ac6 0 + 4342561478 2 libmacruby.dylib 0x000000010014a0b3 rb_vm_dispatch + 1331 3 ??? 0x0000000102d5a536 0 + 4342523190 4 ??? 0x0000000102d63806 0 + 4342560774 5 libmacruby.dylib 0x0000000100162d53 rb_vm_run + 531 6 libmacruby.dylib 0x00000001000408f0 ruby_run_node + 80 7 macruby 0x0000000100000d28 main + 152 8 macruby 0x0000000100000c88 start + 52 Thread 1: 0 libSystem.B.dylib 0x00007fff88fe5f8a __workq_kernreturn + 10 1 libSystem.B.dylib 0x00007fff88fe639c _pthread_wqthread + 917 2 libSystem.B.dylib 0x00007fff88fe6005 start_wqthread + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00007fff5fbfddc0 rbx: 0x0000000000000000 rcx: 0x00007fff5fbfdf0f rdx: 0x0000000000000000 rdi: 0x00000002000bed00 rsi: 0x00000002000bec00 rbp: 0x00007fff5fbfdf40 rsp: 0x00007fff5fbfdcf8 r8: 0x0000000200000000 r9: 0x0000000000000005 r10: 0x0000000000000001 r11: 0x0000000100af9000 r12: 0x00000002000bec00 r13: 0x0000000000000000 r14: 0x0000000000000005 r15: 0x0000000000000000 rip: 0x0000000000000000 rfl: 0x0000000000010246 cr2: 0x0000000000000000 Binary Images: 0x100000000 - 0x100000ff7 +macruby ??? (???) <4408616F-9F77-025F-C278-91F945728AB0> /usr/local/bin/macruby 0x100003000 - 0x100a29fd7 +libmacruby.dylib 0.8.0 (compatibility 0.8.0) <8910242D-90F3-32AC-A4CA-99D5C316AEB8> /Library/Frameworks/MacRuby.framework/Versions/0.8/usr/lib/libmacruby.dylib 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld 0x7fff801f1000 - 0x7fff802aafff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib 0x7fff802ba000 - 0x7fff80478fff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <781E7B63-2AD0-E9BA-927C-4521DB616D02> /usr/lib/libicucore.A.dylib 0x7fff809d0000 - 0x7fff80a8dff7 com.apple.CoreServices.OSServices 357 (357) <7B22626F-D544-1955-CC53-240F4CACEB4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x7fff815d5000 - 0x7fff815ebfef libbsm.0.dylib ??? (???) <42D3023A-A1F7-4121-6417-FCC6B51B3E90> /usr/lib/libbsm.0.dylib 0x7fff817b9000 - 0x7fff817bdff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib 0x7fff81cbb000 - 0x7fff81d05ff7 com.apple.Metadata 10.6.3 (507.15) <5170FCE0-ED6C-2E3E-AB28-1DDE3F628FC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff8208d000 - 0x7fff82310ff7 com.apple.Foundation 6.6.4 (751.42) <AF1E3050-3503-8714-8274-EA6BD6BE8A22> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff82318000 - 0x7fff82340fff com.apple.DictionaryServices 1.1.2 (1.1.2) <E9269069-93FA-2B71-F9BA-FDDD23C4A65E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x7fff8234d000 - 0x7fff8234dff7 com.apple.CoreServices 44 (44) <DC7400FB-851E-7B8A-5BF6-6F50094302FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x7fff8353c000 - 0x7fff83588fff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib 0x7fff83ecb000 - 0x7fff83ed9ff7 libkxld.dylib ??? (???) <27713C39-0E51-8F5A-877B-C5539C96A520> /usr/lib/system/libkxld.dylib 0x7fff8400d000 - 0x7fff84184fe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff85109000 - 0x7fff85144fff com.apple.AE 496.4 (496.4) <55AAD5CA-7160-7899-1C68-562ED8160DF7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x7fff8532d000 - 0x7fff853bdfff com.apple.SearchKit 1.3.0 (1.3.0) <4175DC31-1506-228A-08FD-C704AC9DF642> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff85405000 - 0x7fff85416ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <97019C74-161A-3488-41EC-A6CA8738418C> /usr/lib/libz.1.dylib 0x7fff8688b000 - 0x7fff869a2fef libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <B2FB9DA8-6EC9-FFBC-C919-C022B9CBEB73> /usr/lib/libxml2.2.dylib 0x7fff86a93000 - 0x7fff86af3fe7 com.apple.framework.IOKit 2.0 (???) <D107CB8A-5182-3AC4-35D0-07068A695C05> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff874bc000 - 0x7fff87539fef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib 0x7fff87940000 - 0x7fff87a12fe7 com.apple.CFNetwork 454.11.5 (454.11.5) <5D68598D-C138-C8B6-B6AC-B1F48B01E021> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x7fff8810b000 - 0x7fff881abfff com.apple.LaunchServices 362.2 (362.2) <A8EDC37C-1D40-5ED0-49BE-90EF110A6B3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x7fff88462000 - 0x7fff886e8fff com.apple.security 6.1.1 (37594) <1B4E1ABD-1BB3-DA49-F574-0EEB23E73C6A> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff886ea000 - 0x7fff886f9fff com.apple.NetFS 3.2.1 (3.2.1) <E5D33870-27D2-E50B-9B35-16AA50369733> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x7fff88806000 - 0x7fff88b3afff com.apple.CoreServices.CarbonCore 861.23 (861.23) <96465459-6536-3FD7-7504-B59D0390EEC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff88bcb000 - 0x7fff88c81fff libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <99CB3A0F-64CF-1D16-70CD-8AED2EF06C30> /usr/lib/libobjc.A.dylib 0x7fff88e3d000 - 0x7fff88e7efff com.apple.SystemConfiguration 1.10.5 (1.10.2) <FB39F09C-57BB-D8CC-348D-93E00C602F7D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x7fff88e7f000 - 0x7fff88e85ff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff88f93000 - 0x7fff88fbeff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib 0x7fff88fcb000 - 0x7fff8918cfff libSystem.B.dylib 125.2.1 (compatibility 1.0.0) <F00A8B2F-84A0-0868-1047-3A13F9114864> /usr/lib/libSystem.B.dylib 0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <F00A8B2F-84A0-0868-1047-3A13F9114864> /usr/lib/libSystem.B.dylib

5 16

MacRuby Unit Test Code Coverage
by Gabriel Ayuso 13 Feb '11

13 Feb '11

MacRuby is great for testing not only MacRuby code but also Objective-C code. I find it nicer than using OCTest and OCMock. Is there a way to use existing code coverage tools such as rcov or gcov to check the coverage of MacRuby unit tests? Thanks, Gabriel Ayuso

1 0

Re: [MacRuby-devel] book idea - "making it look like Ruby"
by Arthur Gunn 13 Feb '11

13 Feb '11

> Ruby is extremely flexible. I'm quite sure that some > metaprogramming could be used to prototype something > for experimentation. For the sake of experimentation then, here's some ruby code that does that: https://gist.github.com/824163 I don't think that implementing this in macruby would be a terrible idea. It's not like the way in which the two styles are switched between would be arbitrary, there would be two simple methods for moving each way like String#camelize and String#underscore in rails. One downside I can see is that it could make searching for method names harder. -Arthur

5 6

sprintf, String#%, stringWithFormat, NSLog and friends
by Caio Chassot 12 Feb '11

12 Feb '11

So everything in ruby is an object, which means that when using format strings with Objective-C methods like String+stringWithFormat and NSLog, the only formatter that makes sense is "%@". Other formatters generally give unexpected results. E.g. "%d" will print the value of the pointer to the number object. (Or I think that's what it is.) OTOH ruby itself is, by necessity, smarter in its own handling of format strings. Kernel#sprintf and String#% will generally figure out a way to shoehorn whatever object you're passing into the necessary format, e.g.: "%d" % "4" # => "4" "%d" % 4.1 # => "4" Assorted observations: - Newcomers will inevitably run into sad situations trying to use NSLog with %d and getting really weird numbers. - The inconsistency between the Objective-C and Ruby behaviors still feels weird even though I understand why it is that way. - As far as I know, there' no way to specify a non-object argument value (e.g. int) in a ruby method call. - I'm not sure there's a sane solution to this, e.g. if it's safe to translate ruby objects into the necessary native C types on the fly. - I wonder if, even after being painfully aware of this dichotomy, there will still be pitfalls that can't be worked around: - For example, how do I deal with localizedStringWithFormat? Ruby's native methods aren't locale-aware. - Or what about .strings localization files in a mixed Objective-C / MacRuby app? Has this been given any thought? What are the current plans / recommendations?

1 0

Re: [MacRuby-devel] book idea - "making it look like Ruby"
by Matt Aimonetti 12 Feb '11

12 Feb '11

Magically converting a snake_case method call to a CamelCase method dispatch is bad for peformance and documentation. I believe that Laurent addressed that topic a few times already but I might be wrong. There is currently no plan to support that approach in MacRuby. - Matt On Fri, Feb 4, 2011 at 1:32 PM, Rich Morin <rdm(a)cfcl.com> wrote: > At 6:57 PM -0200 2/4/11, Caio Chassot wrote: > > On 2011-02-04, at 01:26 , Rich Morin wrote: > > I'm sure the situation in JRuby land is worse, but > > generally, using Cocoa stuff from MacRuby feels > > enough like ruby, save for the HorridCamelCase, > > but I've gotten used to that. > > Interestingly, JRuby does quite a bit of work to let > folks use snake_case, instead of CamelCase. > > -r > -- > http://www.cfcl.com/rdm Rich Morin > http://www.cfcl.com/rdm/resume rdm(a)cfcl.com > http://www.cfcl.com/rdm/weblog +1 650-873-7841 > > Software system design, development, and documentation > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >

6 11

Core Data / MacRuby article
by Morgan Schweers 11 Feb '11

11 Feb '11

Greetings, I would love feedback on an article I just put together describing how I'm using Core Data (mainly just finding data, creation is another ball of wax that I haven't tried to make more Ruby-ish yet) in an application I'm building. The article is at: http://cyberfox.com/blog The key code is at: http://gist.github.com/818182 if you want to dive in and try to make sense of it. Any feedback would be wonderful; it appears to work for me, but if there are any issues or better ways to do what I'm doing, I'd love to hear from folks who know better. I'm also not a really great technical writer, so feedback on how it's written is also welcome. Thanks muchly! -- Morgan Schweers

3 2

macruby_deploy changes
by Laurent Sansonetti 10 Feb '11

10 Feb '11

Hi guys, For those who are not following trunk, macruby_deploy got some changes recently: - The --gem option is added. This option will embed the given RubyGem and its dependencies inside the application's bundle. ex. $ macruby_deploy --embed --gem nokogiri Foo.app - The --bs option is added. This option will embed the system BridgeSupport files inside the application's bundle. This can be useful if you rely on BridgeSupport preview. ex. $ macruby_deploy --embed --bs Foo.app - A bug has been fixed, when macruby_deploy was called with --embed but not --compile. The main application executable would not have its load path updated. This was a serious problem. - When using --embed, the 'Current' symlink of the framework is now deleted. Apparently this fixes the Mac AppStore validation process which was following both '0.9' and 'Current' symlinks and ending with a "Payload not declared in Package info" error. Please give tonight's nightly build a try and let us know if you find something wrong :) Laurent

1 0

error: gc operation on unregistered thread
by Joel Reymont 10 Feb '11

10 Feb '11

I get a bunch of errors like this when running the hellofs MacFUSE example [1]: macruby(25346,0x107082000) malloc: *** auto malloc[25346]: error: GC operation on unregistered thread. Thread registered implicitly. Break on auto_zone_thread_registration_error() to debug. Is this a MacRuby problem? How do I fix it? Thanks, Joel [1] http://www.macruby.org/trac/ticket/922 -------------------------------------------------------------------------- - mac osx device driver ninja, kernel extensions and user-land usb drivers ---------------------+------------+--------------------------------------- http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont ---------------------+------------+---------------------------------------

2 1