News for hackers. Stuff that matters.

A comment on If Java Is Dying, It Sure Looks Awfully Healthy. Parent comment

Re:If Java Is Dying, It Sure Looks Awfully Healthy by EpicEng on Thursday October 10, 2013 @03:42AM (#6526210)
I've written a lot of C# and Java (and others of course). It's really not an issue. If you're doing something expensive in a property getter or setter you're doing it wrong. If the function call doesn't get inlined and becomes a bottleneck in some tight loop you can just change it. Anecdotally, I have yet to see this occur in practice.

Also, as the guy below me pointed out, by convention you know that Foo is a property.

[ Parent | on HN ]
Re:If Java Is Dying, It Sure Looks Awfully Healthy by prawks on Thursday October 10, 2013 @09:11AM (#6527364)
Exactly. It's (at least from what I've seen/read) common convention to make sure that getters/setters should be quick and have minimal side effects.

Your application shouldn't hang from a database call when you pull a property from an object. And obviously, methods doing such things should be documented appropriately.

[ Parent | on HN ]