-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"@" instead of "this." #10
Comments
Is this keyword really usefull ? I mean, if all the properties owned by the object are private and immutable, why should we add this keyword to access these properties ? Same for the methods. |
@monsieurluge |
@monsieurluge well, but what about method arguments? We have to distinguish them somehow from attributes:
See? |
Of course, but in many case it's just a naming convention issue. "@" reminds me annotations. But, i agree that it's a very short way to see where are the object's properties. If you want to keep a keyword, why not "self" ? The object is composed by its internal properties so the "self" keyword sounds better for me in an object oriented context. |
I like the word, IMO It's better to use only one way, one style. |
@mdbs99 I also like |
pull request is here: #18 If there are no strong objectives, I will merge it |
no objectives, merged :) |
How about we use
@
sign in front of attribute names instead ofthis.
(like in Java)? Sounds practical to me. This is how Ruby works.The text was updated successfully, but these errors were encountered: