Quote:
Originally Posted by Inverness
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.
|
Haha, I knew Python was going to come up one time or another in this topic
The thing is in other scripting languages, such as PHP, keywords are used and work fine and I actually PREFER them. It makes it much much clearer to see how certain variables are declared and how they should be used, looking through a script. That, COUPLED with the convention, it's a winner, in my opinion.
Can you explain how Graal is TOO dynamic for keywords? How have you come to that conclusion?
Quote:
|
Originally Posted by Inverness
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.
|
Aye, you're not a miracle worker. It also disppoints me to hear your lack of consideration and interest in up and coming scripters.
Overestimating your influence? You've had influence over MANY a scripter. Maybe you're blind to this, because of your lack of consideration for new scripting talent, maybe?
Quote:
|
Originally Posted by Inverness
With Graal scripters it's much better to force them to do it a certain way, they just don't follow convention.
|
I don't think taking a forced approach is the best way. Many scripters, after a while of scripting, explore other languages. They need to learn that, although optional, convention is still important.