Quote:
Originally Posted by Arkshine
one and only one default style ( AINSI ).
|
*ANSI
There isn't any default style. If you start programming in C, you'll see mostly codes using K&R, just as you see in Java. But if you start programming in Python, for example, there's no style at all (in Python, indents define code blocks); if you start programming in Lisp, you'll think all other styles are strange. A cleaner style for one might be a completely different style for others.
Quote:
Originally Posted by Arkshine
The first thing to do should be learning the very basics of the language.
|
That's the point. Learning the basics of the language means learning to catch identifiers easily, and by doing so understanding the code no matter what style it uses. For example, the Pawn Language Guide, designed to beginners in Pawn, uses GNU's coding style convention, which I think is one of the ugliest, not used styles, but still, everyone can understand what it does.
Quote:
Originally Posted by Arkshine
If all plugins were using the same style and with consistent coding, there would be more users enjoying the coding.
|
If you really have difficulties with one particular code style, you can use a source code formatter.
We're not writing big source for big projects, we are scripting, and in the scripting world, the maintainer of the source is almost always the creator.
My final opinion is that: When you're reading someone else's code, you have to respect the author choice. And I say more, you have to use his coding style to learn his code. Many programmers have particular choices while coding that helps us, readers, to find important sections of the code. Like I said, if you really can't read other styles, you can always use a source code formatter.