UNLOZE/sourcemod
10
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Documentation oddities for Call_PushStringEx

Browse Source 
See changes for details, should be obvious. What also strikes me as odd is that there is only one cpflag atm. Has this always been the case? Will there be more in the future? Or why is this designed to be a flagstring?
This commit is contained in:
InstantMuffin 2015-03-05 20:47:05 +01:00
parent 6f8ffd55a7
commit 3f2ad5ccb0
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
plugins/include/functions.inc
View File

@ -318,10 +318,10 @@ native Call_PushString(const String:value[]);
* @param value String to push. * @param value String to push.
* @param length Length of string buffer. * @param length Length of string buffer.
* @param szflags Flags determining how string should be handled. * @param szflags Flags determining how string should be handled.
* See SP_PARAM_STRING_* constants for details. * See SM_PARAM_STRING_* constants for details.
* The default (0) is to push ASCII. * The default (0) is to push UTF-8.
* @param cpflags Whether or not changes should be copied back to the input array. * @param cpflags Whether or not changes should be copied back to the input array.
* See SP_PARAM_* constants for details. * See SM_PARAM_* constants for details.
* @noreturn * @noreturn
* @error Called before a call has been started. * @error Called before a call has been started.
*/ */