StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>No, not for now :(</p> <p>From the <a href="https://github.com/jashkenas/coffee-script/wiki/FAQ" rel="nofollow noreferrer">CoffeeScript FAQ</a>:</p> <blockquote> <p>Q: Will you add feature X where feature X depends on a platform? </p> <p>A: No, implementation-specific features are not allowed as a policy. Everything that you write in CoffeeScript should be supported and runnable on any current JavaScript implementation (in practice, this means the lowest common denominator is IE6). Thus, features such as the following will not be implemented: getters & setters, yield. </p> </blockquote> <p>Some GitHub issues about getter & setter syntax: <a href="https://github.com/jashkenas/coffee-script/issues/64" rel="nofollow noreferrer">#64</a>, <a href="https://github.com/jashkenas/coffee-script/issues/451" rel="nofollow noreferrer">#451</a>, <a href="https://github.com/jashkenas/coffee-script/issues/1165/" rel="nofollow noreferrer">#1165</a> (there is some nice discussion in the last one). </p> <p>I personally think that having getter & setter literal syntax would be a nice opt-in feature for CoffeeScript now that <code>defineProperty</code> is <a href="http://ecma-international.org/ecma-262/5.1/" rel="nofollow noreferrer">part of the ECMAScript standard</a>. The need for getters & setters in JavaScript can be questionable, but you're not forced to use them just because they exist. </p> <hr> <p>Anyway, as you noticed, it's not that hard to implement a convenient wrapper function that calls <code>Object.defineProperty</code> for class declarations. I personally would use the approach suggested in <a href="https://github.com/jashkenas/coffee-script/issues/451#issuecomment-2404226" rel="nofollow noreferrer">here</a>:</p> <pre><code>Function::property = (prop, desc) -> Object.defineProperty @prototype, prop, desc class Person constructor: (@firstName, @lastName) -> @property 'fullName', get: -> "#{@firstName} #{@lastName}" set: (name) -> [@firstName, @lastName] = name.split ' ' p = new Person 'Robert', 'Paulson' console.log p.fullName # Robert Paulson p.fullName = 'Space Monkey' console.log p.lastName # Monkey </code></pre> <p>Or, maybe create two different methods:</p> <pre><code>Function::getter = (prop, get) -> Object.defineProperty @prototype, prop, {get, configurable: yes} Function::setter = (prop, set) -> Object.defineProperty @prototype, prop, {set, configurable: yes} class Person constructor: (@firstName, @lastName) -> @getter 'fullName', -> "#{@firstName} #{@lastName}" @setter 'fullName', (name) -> [@firstName, @lastName] = name.split ' ' </code></pre> <p>For plain objects you can just use <code>Object.defineProperty</code> (or <a href="https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Object/defineProperties" rel="nofollow noreferrer"><code>Object.defineProperties</code></a> ;) ) on the object itself as <a href="https://stackoverflow.com/a/11587298/581845">Jason proposed</a>. Maybe wrap that in a little function:</p> <pre><code>objectWithProperties = (obj) -> if obj.properties Object.defineProperties obj, obj.properties delete obj.properties obj rectangle = objectWithProperties width: 4 height: 3 properties: area: get: -> @width * @height console.log rectangle.area # 12 rectangle.width = 5 console.log rectangle.area # 15 </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload