This macro definition crashes the compiler with no outcome.
#7

Quote:
Originally Posted by NaS
View Post
But there's a difference between defining a macro with different arguments that calls a seperate function and a macro that would call itself.

OK:

#define Kick(%1,%2) DelayedKick(%1,%2)

Not OK:

#define Kick(%1,%2) Kick(%1)
So why is these
#define Kick(%1,%2) Kick(%1)
being completely ignored then?

like it's only logical that if it's ended, it's ended. and that I'm only defining for i.ex.
Kick(%1,%2)
to be
Kick(%1)
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 3 Guest(s)