Brynner
Community Contributors
what happen to typedef int?
typedef int (*AtCommandFunc)(const int fd, struct map_session_data* sd, const char* command, const char* message);
it became typedef bool?
typedef bool (*AtCommandFunc)(const int fd, struct map_session_data* sd, const char* command, const char* message,struct AtCommandInfo *info);
what is the correct way to use the typedef int?
typedef int (*AtCommandFunc)(const int fd, struct map_session_data* sd, const char* command, const char* message);
because im getting warnings.
typedef int (*AtCommandFunc)(const int fd, struct map_session_data* sd, const char* command, const char* message);
it became typedef bool?
typedef bool (*AtCommandFunc)(const int fd, struct map_session_data* sd, const char* command, const char* message,struct AtCommandInfo *info);
what is the correct way to use the typedef int?
typedef int (*AtCommandFunc)(const int fd, struct map_session_data* sd, const char* command, const char* message);
because im getting warnings.
Code:
srcmapatcommand.c(9694): warning C4113: 'int (__cdecl *)(const int,map_session_data *,const char *,const char *)' differs in parameter lists from 'AtCommandFunc'srcmapatcommand.c(9694): warning C4133: 'initializing' : incompatible types - from 'int (__cdecl *)(const int,map_session_data *,const char *,const char *)' to 'AtCommandFunc'