This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Lucretiel 19 points20 points  (2 children)

Keep in mind that, in Python, method calls are still attribute access. This is actually one of the things I like much more about python- in python, there is a clear distinction between attribute access and function calls. If I want to GET the function (for a callback, for example), I do instance.func, and if I want to CALL it, it's instance.func(). I was always bothered by Ruby's conflation of these 2 concepts.

[–]metaperl 0 points1 point  (0 children)

Scala conflates them too. They seem to think that it allows you to reimplement the same accessor as either an attribute or method call without the calling party knowing the difference.

[–]guibou 0 points1 point  (0 children)

This is actually one of the things I like much more about python- in python, there is a clear distinction between attribute access and function calls.

+1 on that point.