[~Ice*shOt]

Will it somehow affect plugin if there's one or a lot of defines like that?

PHP Code:

#define    SetHealth(%1)        set_user_health(%1) 


[Obada]

I don't think so.

[~Ice*shOt]

So there will be exactly the same if I use

PHP Code:

set_user_health(id) 


or I'll define

PHP Code:

#define    SetHealth(%1)        set_user_health(%1) 


and use SetHealth(id)

[fysiks]

Originally Posted by ~Ice*shOt Will it somehow affect plugin if there's one or a lot of defines like that? PHP Code: #define    SetHealth(%1)        set_user_health(%1)

No. But, you've done it wrong for this function, set_user_health() requires two arguments.\

It would probably help if you know what a #define actually does. It replaces the defined 'thing' with it's definition at compile time. So, after you compile it, the code will no longer contain "SetHealth()", it will contain only it's definition "set_user_health()".

[~Ice*shOt]

So it doesn't make sense I use my defined function or original, thanks.

[Bugsy]

Originally Posted by ~Ice*shOt So it doesn't make sense I use my defined function or original, thanks.

They are useful for not having to re-write things over and over again. You still need to call the macro, but you can avoid repeating parts of it that are constant.

PHP Code:

//ie. instead of 
set_user_health( id , 100 )

//you would just do 
#define SetHealth(%1)   set_user_health(%1, 100) 

//Then in code, you can leave out the 100 part and just do 
SetHealth( id ) 


At compile, as fysiks said, every instance of SetHealth(val ) is replaced with set_user_health( val , 100 ). There's no damage or benefit on performance.

Also, for things like this it makes it a lot easier to use the macro instead of writing it out multiple times:

PHP Code:

#define SetBit(%1)   (g_Bits |= (1<<%1))
#define ClearBit(%1)   (g_Bits &= ~(1<<%1)) 


[~Ice*shOt]

Thanks!