[Macluawn]

I wouldnt say that this is the worst part, but it tends to consume a lot of time:
Choosing a name for a variable (or function, structure etc.) that best describes it. I find myself looking through online dictionaries quite often.

[Slice]

Testing and documentation.. I just want to make stuff!

[DobbysGamertag]

Quote:

Originally Posted by Slice Testing and documentation.. I just want to make stuff!

Not the only one. I've ran out of ideas for VIP commands now there's rc cars added to my server. 4 dragons casino etc. Now i'm just focusing on adding missions (fun fun fun -_-) and getting rid of the bugs.

[RajatPawar]

The worst part is writing how to use your include or code and then answer stupid questions like "cannot load it"! About scripting, it's having to wait for a huge script to compile.

[zgintasz]

are you sure testing and writing documentation is part of scripting?

[Sinner]

Quote:

Originally Posted by zgintasz are you sure testing and writing documentation is part of scripting?

Sure as heck no-one else is gonna do it for you. Yes, it's deffinately part of scripting.

[Y_Less]

Quote:

Originally Posted by zgintasz are you sure testing and writing documentation is part of scripting?

Yes, otherwise how do you know if it works or what it does? By that logic you could argue that gathering co-ordinates isn't scripting, or that designing database schema isn't scripting either.

[Vince]

Didn't a topic like this already exist somewhere? https://sampforum.blast.hk/showthread.php?tid=351455

[MP2]

Quote:

Originally Posted by Y_Less Yes, otherwise how do you know if it works or what it does? By that logic you could argue that gathering co-ordinates isn't scripting, or that designing database schema isn't scripting either.

IMO gathering coordinates ISN'T scripting. 'Scripting' - writing a script - since when is typing /save writing a script?

[JohnnyChen]

I agree with you . Is very usefull!

[Riddick94]

Quote:

Originally Posted by DobbysGamertag I have a new "worst part". Realising you can: pawn Code: #define C CMD //defining c as CMD. Such a noob mistake

Alright.. but this one:

pawn Code:

#define clrscr(); SYSTEM("CLS");

Is the same right? That's what my tutor's doing when I tried to set some value to macro, just like I'm doing it in PAWN, what I mean exactly is:

pawn Code:

#define SOMETHING   (15)

But he told me to use:

pawn Code:

unsigned int SOMETHING = 15;

Is he right, or not really? That was in C programming.

[Y_Less]

C macros are different to PAWN ones (they're actually a lot LESS powerful).