Quote:
Originally Posted by xXziroXx
I don't understand you two and your "lack of formal documentation" - it's working good enough so far for the majority of programmers on Graal. If you don't know something, then you ask on the forums, which happen how often?
|
I still don't know what the second parameter of GuiMLTextCtrl.addtext() does and I shouldn't have to ask on the forum for something so simple.
Quote:
Originally Posted by xXziroXx
Everything you need to know is on the wiki, more or less. And if you want documentation, how about contributing to the wiki yourselves once in a while? Graal is community run, and always have been. :/
|
When you create a scripting language you don't leave other people to document it for you.
Quote:
Originally Posted by Skyld
No no no! People already get confused trying to mix old and new GScript. Adding more languages will just make that worse.
|
If we do it like I suggest then there wont be any mixing at all.
Quote:
Originally Posted by Skyld
Do you honestly think that every other language in the world is based upon reading a manual and instantly understanding everything? There are IRC channels on the Internet with hundreds of thousands of users asking questions about scripting languages, and there are Usenet groups on the Internet with hundreds of thousands of users asking questions about scripting languages, and forums on the Internet with hundreds of thousands of users asking questions about scripting languages.
|
I'm sure people those people don't ask what parameter goes where in a function because the documentation only says string or integer but not what its for.
Lack of documentation and consistence is exactly my issue with GScript. I don't like how dynamic variable are case-sensitive yet static variables aren't. I don't like how declaring a variable without a prefix that isn't already declared temp is made a global variable.
Python is a well documented and developed scripting language with Stackless offering features that would be quite useful to Graal. The Python doc strings are in the function and member definitions themselves so you've got your documentation method right there in your source code.