January 2009 - MacRuby-devel - lists.macosforge.org

[MacRuby] #166: Bus error when installing gem
by MacRuby 13 Jan '09

13 Jan '09

#166: Bus error when installing gem --------------------------------------+------------------------------------- Reporter: mail@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: MacRuby 0.4 Component: MacRuby | Keywords: --------------------------------------+------------------------------------- Whenever I try to install a Gem macruby crashes with a bus error. I attached a strack trace for when I tried to install the Amazon S3 gem. -- Ticket URL: <http://www.macruby.org/trac/ticket/166> MacRuby <http://macruby.org/>

1 1

[MacRuby] #204: Private methods redefined public are still in private_methods
by MacRuby 10 Jan '09

10 Jan '09

#204: Private methods redefined public are still in private_methods ----------------------------------------+----------------------------------- Reporter: vincent.isambart@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ----------------------------------------+----------------------------------- All classes have a private puts method. However, if you redefine publically puts in a class, puts is still in its private methods list (but it's also in the public methods). It should only be in the public methods. {{{ class A; end p A.private_instance_methods.grep(/puts/) p A.public_instance_methods.grep(/puts/) class A def puts end end p A.private_instance_methods.grep(/puts/) p A.public_instance_methods.grep(/puts/) }}} displays: {{{ [:puts] [] [:puts] [:puts] }}} instead of: (Ruby 1.9) {{{ [:puts] [] [] [:puts] }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/204> MacRuby <http://macruby.org/>

1 1

Pointers for BOOL types
by Dr Nic Williams 10 Jan '09

10 Jan '09

The following method takes a ptr->BOOL. I've played around but cannot figure out how to create a pointer to a true/false that then returns true/false via its accessor. - (BOOL)fileExistsAtPath:(NSString *)path isDirectory:(BOOL *)isDirectory The following doesn't work: framework 'Cocoa' p1 = Pointer.new_with_type('@') p1.assign(false) p1[0] == false # => false, but should be true Then I figured I should be able to pass BOOL to -new_with_type as it is the data type, but BOOL isn't recognised. Perhaps test_objc.rb could include some more examples/coverage of Pointer usage too? -- Dr Nic Williams iPhone and Rails consultants - http://mocra.com Fun with iPhone/Ruby/Rails/Javascript - http://drnicwilliams.com * Surf Report for iPhone - http://mocra.com/projects/surfreport/ *

6 10

[MacRuby] #203: Marshal.dump does not serialize an Exception's backtrace
by MacRuby 10 Jan '09

10 Jan '09

#203: Marshal.dump does not serialize an Exception's backtrace ----------------------------------------+----------------------------------- Reporter: vincent.isambart@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ----------------------------------------+----------------------------------- The following code: {{{ begin raise 'test' rescue Exception => e p e.backtrace p Marshal.load(Marshal.dump(e)).backtrace end }}} displays: {{{ ["untitled.rb:2:in `<main>'"] nil }}} instead of: (Ruby 1.9) {{{ ["untitled.rb:2:in `<main>'"] ["untitled.rb:2:in `<main>'"] }}} If you look at the (binary) result of Marshal.dump(e), you can indeed see that it does not include the backtrace in MacRuby. -- Ticket URL: <http://www.macruby.org/trac/ticket/203> MacRuby <http://macruby.org/>

1 0

MacRuby 0.5???
by Brad Hutchins 08 Jan '09

08 Jan '09

Wasn't there an update for MacRuby 0.5 suppose to be released soon? Brad

2 1

[MacRuby] #112: NSNumber should behave consistently regardless of how it is accessed
by MacRuby 08 Jan '09

08 Jan '09

#112: NSNumber should behave consistently regardless of how it is accessed -------------------------------------+-------------------------------------- Reporter: jordan.breeding(a)mac.com | Owner: lsansonetti(a)apple.com Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- Currently if an NSNumber is stored in something (like an NSDictionary) it behaves differently depending on how you access it. Accessing it through Cocoa methods gets you a raw NSCFNumber which doesn't work with ruby methods, accessing it through [] gets you a ruby object that works. {{{ 6 jordan@thetourist ~/Desktop/Scripts > macirb >> framework("Cocoa") => true >> myDict = NSMutableDictionary.dictionary => {} >> NSNumber.numberWithInt(100) => #<NSCFNumber:0x1020fc0> >> myDict.setObject(100, forKey: "testNum1") => nil >> myDict.setObject(NSNumber.numberWithInt(100), forKey: "testNum2") => nil >> myDict.objectForKey("testNum1") => 100 >> myDict.objectForKey("testNum2") => #<NSCFNumber:0x10aaca0> >> myDict.objectForKey("testNum1").to_f => 100.0 >> myDict.objectForKey("testNum2").to_f NoMethodError: undefined method `to_f' for #<NSCFNumber:0x10aaca0> from (irb):9 from /usr/local/bin/macirb:12:in `<main>' >> myDict.objectForKey("testNum1") / 50 => 2 >> myDict.objectForKey("testNum2") / 50 NoMethodError: undefined method `/' for #<NSCFNumber:0x10aaca0> from (irb):11 from /usr/local/bin/macirb:12:in `<main>' >> myDict["testNum1"].to_f => 100.0 >> myDict["testNum2"].to_f => 100.0 >> myDict["testNum1"] / 50 => 2 >> myDict["testNum2"] / 50 => 2 >> }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/112> MacRuby <http://macruby.org/>

1 3

[MacRuby] #198: Bug in class constant lookup.
by MacRuby 07 Jan '09

07 Jan '09

#198: Bug in class constant lookup. -------------------------------------+-------------------------------------- Reporter: eloy.de.enige@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- MacRuby finds namespaced classes when it shouldn't: {{{ module Namespace class Foo end end p Foo # => Namespace::Foo }}} Added test case to known_bugs.rb in r777 -- Ticket URL: <http://www.macruby.org/trac/ticket/198> MacRuby <http://macruby.org/>

1 2

Introduction
by Giampiero De Ciantis 06 Jan '09

06 Jan '09

Hi everyone, I am new to the mailing list. Looking forward to watching MacRuby evolve. Would love to help somehow. -Gp

1 0

Warnings about removing methods
by Eloy Duran 06 Jan '09

06 Jan '09

Hi, Is there a good reason why MacRuby would need to warn the user about the hazzards of removing methods? Removing methods is always a risky business, also in pure Ruby. But this is the power that a Ruby user gets and with it comes responsibility. And since Ruby doesn't warn for this, MacRuby shouldn't do so either IMO. Example: /Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/ site_ruby/mocha/class_method.rb:50: warning: removing pure Objective-C method `__stubba__require__stubba__' may cause serious problem Eloy

3 5

[MacRuby] #197: A removed, or undefined, pure Objective-C method should raise a NoMethodError when called.
by MacRuby 06 Jan '09

06 Jan '09

#197: A removed, or undefined, pure Objective-C method should raise a NoMethodError when called. -------------------------------------+-------------------------------------- Reporter: eloy.de.enige@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- Currently when removing a pure Objective-C method a warning is raised. However, it would be more Ruby-ish if remove_method and undef_method would replace the methods with a stub method which raises a NoMethodError. This way the user will still get a sensible error message when the application crashes, but will not constantly be warned when removing methods. -- Ticket URL: <http://www.macruby.org/trac/ticket/197> MacRuby <http://macruby.org/>

1 0