Create KVC-compliant setter when using attr_accessor.

[alloye@…]

When using attr_accessor, a KVC-compliant setter method is not registered. Adding this feature would allow Ruby classes to be defined using the same semantics as Objective-C 2.0 classes that employ synthesized properties.

[~]: irb
>> framework "Cocoa"
=> true
>> class Person
>> attr_accessor :name
>>   def initialize(name="")
>>     @name = name
>>   end
>> end
=> nil
>> p = Person.new("Wayne Steele")
=> #<Person:0x1847180 @name="Wayne Steele">
>> p.respond_to?("name=")
=> true
>> p.respond_to?("setName:")
=> false

[lsansonetti@…]

You're right, I was thinking the same thing a while ago. This would also eliminate the need of the ib_outlet method.

[lsansonetti@…]

Fixed in r526/trunk.

attr_writer/attr_accessor now generates a KVC-compliant setter. ib_outlet has been deprecated.