03.12.2013, 05:17
The language features that exist should be used to suit the best case scenario for a given situation. Asking for preferences on syntax is fine, but things like #3, "stock" and "public" keywords just show one's lack of knowledge for the language they're using.
For example, when one writes a library they should declare variables (if not all) and functions that are only used internally by the library as static. For the functions called by the script that include the library, but not necessary to be called, should be stock.
I've wanted to write a tutorial describing how to use PAWN properly, but I feel like it would be a waste (just look at YSI).
For example, when one writes a library they should declare variables (if not all) and functions that are only used internally by the library as static. For the functions called by the script that include the library, but not necessary to be called, should be stock.
I've wanted to write a tutorial describing how to use PAWN properly, but I feel like it would be a waste (just look at YSI).