Quote:
Originally Posted by Codein
Yeah, I can see exactly what you mean. However, I still think a keyword would still be best. I mean, I have, for some time, wanted some kind of support for classes, in a traditional sense and keywords for declaring class members would be necessary in my opinion.
|
Python is a very popular language and it implements classes just fine without variable access keywords. Something like private variables are implemented using name mangling with variables prefixed with '__', __e becomes __Pancake_e where Pancake is the name of the class, avoiding collision by inheritance. There isn't an absolute way to prevent variable access and I don't think one is necessary in Python or Graal.
Quote:
Originally Posted by Codein
Also, I don't see you preaching conventions, being in a position of influence within the scripting community. If you shown the importance of them, like many other of the Scripting Elite on here, there should be an improvement in that field.
|
I'm not a miracle worker. I also don't care too much about what other people do as long as I don't have to look at their scripting. And I think you overestimate my influence.
Quote:
Originally Posted by Codein
Regarding your edit, the convention is optional, as with any convention. It's just recommended. There's something about using what LOOKS like a convention as an actual declaration gets to me, for some reason.
|
With Graal scripters it's much better to force them to do it a certain way, they just don't follow convention.