Comments on: Synthesizing Accessor Methods

By: Bruno Scheele

Bruno Scheele — Tue, 13 Sep 2011 19:01:00 +0000

Indeed… it’s stuff like this that I want to know about Cappuccino. Writing a whole lot of boilerplate and only now learning about this is rather disappointing :/

By: Joel Norvell

Joel Norvell — Sun, 22 Nov 2009 08:23:39 +0000

You might consider appending this to the “Learning Objective-J” tutorial at some point.

By: Matthew Brewer

Matthew Brewer — Wed, 14 Oct 2009 04:44:30 +0000

Just wanted to point out that

BOOL _hidden @accessors(getter=isHidden, setter=setIsHidden);

throws an exception in 0.7.1 as the setter requires a semicolon at the end of the selector, ie

BOOL _hidden @accessors(getter=isHidden, setter=setIsHidden:);

Just worth noting.

By: stuffmc

stuffmc — Fri, 29 May 2009 19:03:05 +0000

Guys, maybe it would be a good idea to update the “Learn Objective J” Tutorial with this, don't you think? Actually, what about hiring somebody responsible for the documentation?

By: stuffmc

stuffmc — Sun, 22 Mar 2009 15:45:27 +0000

I would agree with Matteo. I would have loved to just use @property. Ross, could you be more specific about the possible @property implementation in the future? I don't understand how/why you would do that. Are you guys planning to be able to target Cappuccino with Regular Objective C code? That would be certainly very nice if Apple would buy you guys

By: BJH

BJH — Wed, 17 Dec 2008 08:50:27 +0000

Will the tutorials be modified to reflect this new functionality

By: BJH

BJH — Wed, 17 Dec 2008 02:50:27 +0000

Will the tutorials be modified to reflect this new functionality

By: Cappuccino Blog » Blog Archive » Cappuccino 0.6 Available Today

Cappuccino Blog » Blog Archive » Cappuccino 0.6 Available Today — Fri, 12 Dec 2008 03:57:58 +0000

[...] New language addition to Objective-J: The @accessors keyword to eliminate the boiler plate code of writing setters and getters. Read more about it here. [...]

By: boucher

boucher — Sun, 26 Oct 2008 21:19:11 +0000

Zach, I believe this is in fact the current behavior. You should be able to override them without any problems, but let us know if thats not the case.

By: boucher

boucher — Sun, 26 Oct 2008 21:15:17 +0000

I agree. We make considerable effort to stay compatible with Objective-C and Cocoa. However, in this case, the two features are not analogous, and so it doesn't make sense to use the Obj-C 2.0 syntax. Specifically, in the future, we may actually support that feature of Obj-C 2.0, which would potentially create a lot of incompatible code.