[Lordzy]

Quote:

Originally Posted by Misiur It's funny how you linked Y_Less's thread, but explained something completely diffrent. http://forum.sa-mp.com/showthread.ph...593#post819593 1. Include guards are already built-in 2. #include <a/b> should be #include <a\b> 3. In case you have #include <b> and #include <a\b> you might have to get rid of default include guards and substiture them with your implementation 4. #pragma dynamic doesn't change cell size. Cell is always 4 bytes on 32 bit builds

That thread was linked for some basic facts which can be used while creating an include and I don't see anything wrong with it.
About include-guards : If we're including the same file twice, it's true that there won't be any errors/warns. However, it's required in case if other versions of that include is being done and we're naming it anything else. Some releases are there which mostly uses the same part of code but just the include name is renamed.

About the second one, I was also confused for a while in choosing what should be. I've done some tests and it seems like both character usage works fine. If there's something wrong with it, please let me know. An example would be fine.

Third one - I did some test right now, but it seems like things are alright but got chances to have collision as you've told. In such case, I believe it's better for the user to rename the file.

Fourth - Yes, it doesn't change the cell size. It just allows you to get your script compiled with arrays of larger cells. It won't be giving any stack size warning or message in case if higher cells are used under a callback and compiled. I've given this reply on the tutorial also, now.