sscanf 2.8.2
NPC modes
To use sscanf in an NPC mode, download this file:
http://dl.dropbox.com/u/21683085/npcdll.rar
And extract it to your root server directory (so "amxsscanf.dll" is in the same directory as "samp-npc.exe"). Then use as normal. The only tiny difference is that "u", "r", and "q" don't know if a user is a bot or not, so just assume they are all players - use accordingly.
Downloads
GitHub repo (for sscanf 3):
https://github.com/maddinat0r/sscanf/releases
Source, Windows .dll, Linux .so and include:
https://dl.dropboxusercontent.com/u/102595204/sscanf-2.8.2.zip
Use
This behaves exactly as the old sscanf did, just MUCH faster and much more flexibly. To use it add:
#include <sscanf2>
To your modes and remove the old sscanf (the new include will detect the old version and throw an error if it is detected). On windows add:
plugins sscanf
To server.cfg. On Linux add:
plugins sscanf.so
The basic code looks like:
if (sscanf(params, "ui", giveplayerid, amount))
{
? ?return SendClientMessage(playerid, 0xFF0000AA, "Usage: /givecash <playerid/name> <amount>");
}
However it should be noted that sscanf can be used for any text processing you like. For example an ini processor could look like (don't worry about what the bits mean at this stage):
if (sscanf(szFileLine, "p<=>ss", szIniName, szIniValue))
{
? ?printf("Invalid INI format line");
}
There is also an alternate function name to avoid confusion with the C standard sscanf:
if (unformat(params, "ui", giveplayerid, amount))
{
? ?return SendClientMessage(playerid, 0xFF0000AA, "Usage: /givecash <playerid/name> <amount>");
}
Specifiers
The available specifiers (the letters "u", "i" and "s" in the codes above) are below.
? ?
Specifier(s) ? ? ? ? ? ? ? Name ? ? ? ? ? ? ? ? ? Example values
? ?i, d ? ? ? ? Integer ? ? ? ? ? ? ? ? ? ? ? ? ? ?1, 42, -10
? ?c ? ? ? ? ? ?Character ? ? ? ? ? ? ? ? ? ? ? ? ?a, o, *
? ?l ? ? ? ? ? ?Logical ? ? ? ? ? ? ? ? ? ? ? ? ? ?true, false
? ?b ? ? ? ? ? ?Binary ? ? ? ? ? ? ? ? ? ? ? ? ? ? 01001, 0b1100
? ?h, x ? ? ? ? Hex ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?1A, 0x23
? ?o ? ? ? ? ? ?Octal ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?045 12
? ?n ? ? ? ? ? ?Number ? ? ? ? ? ? ? ? ? ? ? ? ? ? 42, 0b010, 0xAC, 045
? ?f ? ? ? ? ? ?Float ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?0.7, -99.5
? ?g ? ? ? ? ? ?IEEE Float ? ? ? ? ? ? ? ? ? ? ? ? 0.7, -99.5, INFINITY, -INFINITY, NAN, NAN_E
? ?u ? ? ? ? ? ?User name/id (bots and players) ? ?Y_Less, 0
? ?q ? ? ? ? ? ?Bot name/id ? ? ? ? ? ? ? ? ? ? ? ?ShopBot, 27
? ?r ? ? ? ? ? ?Player name/id ? ? ? ? ? ? ? ? ? ? Y_Less, 42
? ?
The specifier "s" is used, as before, for strings - but they are now more advanced. As before they support collection, so doing:
sscanf("hello 27", "si", str, val);
Will give:
hello
27
Doing:
sscanf("hello there 27", "si", str, val);
Will fail as "there" is not a number. However doing:
sscanf("hello there", "s", str);
Will give:
hello there
Because there is nothing after "s" in the specifier, the string gets everything. To stop this simply add a space:
sscanf("hello there", "s ", str);
Will give:
hello
You can also escape parts of strings with "\\" - note that it is two backslashes as 1 is used by the compiler:
sscanf("hello\\ there 27", "si", str, val);
Will give:
hello there
27
All these examples however will give warnings in the server as the new version has array sizes. The above code should be:
new
? ?str,
? ?val;
sscanf("hello\\ there 27", "si", str, val);
As you can see - the format specifier now contains the length of the target string, ensuring that you can never have your strings overflow and cause problems. This can be combined with the SA:MP compiler's stringizing:
#define STR_SIZE 32
new
? ?str,
? ?val;
sscanf("hello\\ there 27", "si", str, val);
So when you change your string size you don't need to change your specifiers.
What happened to "z", the optional string? z has been removed (you can still use it but will get a server warning) to make way for the new optional parameter system described later on.
? ?
One of the advanced new specifiers is "a", which creates an array, obviously. The syntax is similar to that of strings and, as you will see later, the delimiter code:
new
? ?arr;
sscanf("1 2 3 4 5", "a<i>", arr);
The "a" specifier is immediately followed by a single type enclosed in angle brackets - this type can be any of the basic types listed above. It is the followed, as with strings now, by an array size. The code above will put the numbers 1 to 5 into the 5 indexes of the "arr" array variable.
Arrays can now also be combined with strings (see below), specifying the string size in the array type:
a<s[10]>[12]
This will produce an array of 12 strings, each up to 10 characters long (9 NULL). Optional string arrays still follow the optional array syntax:
A<s[10]>(hello)[12]
However, unlike numbers you can't specify a progression and have it fill up. This code:
A<i>(0, 1)[4]
Will by default produce:
0, 1, 2, 3
However, this code:
A<s[10]>(hi, there)[4]
Will by default produce:
"hi, there", "hi, there", "hi, there", "hi, there"
As normal, you can add brackets in to the default string value with "\)":
A<s[10]>(hi (code\))[4]
It should also be noted that there is NO length checking on default strings. If you do:
A<s[10]>(This is longer than 10 characters)[4]
You will probably just corrupt the PAWN stack. The length checking is to ensure no users enter malicious data; however, in this case it is up to the scripter to ensure that the data is correct as they are the only one affecting it and shouldn't be trying to crash their own server. Interestingly, arrays of strings actually also work with jagged arrays and arrays that have been shuffled by Slice's quicksort function (this isn't a side-effect, I specifically wrote them to do so).
? ?
This is possibly the most powerful addition to sscanf ever. This gives you the ability to define the structure of an enum within your specifier string and read any data straight into it. The format takes after that of arrays, but with more types - and you can include strings in enums (but not other enums or arrays):
enum
? ?E_DATA
{
? ?E_DATA_C,
? ?Float:E_DATA_X,
? ?E_DATA_NAME,
? ?E_DATA_Z
}
main
{
? ?new
? ? ? ?var;
? ?sscanf("1 12.0 Bob c", "e<ifsc>", var);
}
Now I'll be impressed if you can read that code straight off, so I'll explain it slowly:
e - Start of the "enum" type
< - Starts the specification of the structure of the enum
i - An integer, corresponds with E_DATA_C
f - A float, corresponds with E_DATA_X
s - A 32 cell string, corresponds with E_DATA_NAME
c - A character, corresponds with E_DATA_Z
> - End of the enum specification
Note that an enum doesn't require a size like arrays and strings - it's size is determined by the number and size of the types. Most, but not all, specifiers can be used inside enums (notably arrays and other enums can't be).
? ?
The two new specifiers "{" and "}" are used for what are known as "quiet" strings. These are strings which are read and checked, but not saved. For example:
sscanf("42 -100", "{i}i", var);
Clearly there are two numbers and two "i", but only one return variable. This is because the first "i" is quiet so is not saved, but affects the return value. The code above makes "var" "-100". The code below will fail in an if check:
sscanf("hi -100", "{i}i", var);
Although the first integer is not saved it is still read - and "hi" is not an integer. Quiet zones can be as long as you like, even for the whole string if you only want to check values are right, not save them:
sscanf("1 2 3", "i{ii}", var);
sscanf("1 2 3", "{iii}");
sscanf("1 2 3", "i{a<i>}", var);
You can also embed quiet sections inside enum specifications:
sscanf("1 12.0 Bob 42 INFINITY c", "e<ifs{ig}c>", var);
Quiet sections cannot contain other quiet sections, however they can include enums which contain quiet sections.
? ?
Searches were in the last version of sscanf too, but I'm explaining them again anyway. Strings enclosed in single quotes (') are scanned for in the main string and the position moved on. Note that to search for a single quote you escape it as above using "\\":
sscanf("10 11 woo 12", "i'woo'i", var0, var1);
Gives:
10
12
You could achieve the same effect with:
sscanf("10 11 woo 12", "i{is}i", var0, var1);
But that wouldn't check that the string was "woo". Also note the use of "1000" for the string size. Quiet strings must still have a length, but as they aren't saved anywhere you can make this number as large as you like to cover any eventuality. Enum specifications can include search strings.
? ?
This is a feature similar to quiet sections, which allows you to skip overwriting certain parts of an enum:
e<ii-i-ii>
Here the "-" is a "minus", and tells sscanf that there is an enum element there, but not to do anything, so if you had:
enum E
{
? ?E_A,
? ?E_B,
? ?E_C,
? ?E_D,
? ?E_E
}
And you only wanted to update the first two and the last fields and leave all others untouched you could use that specifier above. This way sscanf knows how to skip over the memory, and how much memory to skip. Note that this doesn't read anything, so you could also combine this with quiet sections:
e<ii-i-i{ii}i>
That will read two values and save them, skip over two memory locations, read two values and NOT save them, then read and save a last value. In this way you can have written down all the values for every slot in the enum, but have only used 3 of them. Note that this is the same with "E" - if you do:
E<ii-i-ii>
You should ONLY specify THREE defaults, not all five:
E<ii-i-ii>(11, 22, 55)
? ?
The previous version of sscanf had "p" to change the symbol used to separate tokens. This specifier still exists but it has been formalised to match the array and enum syntax. What was previously:
sscanf("1,2,3", "p,iii", var0, var1, var2);
Is now:
sscanf("1,2,3", "p<,>iii", var0, var1, var2);
The old version will still work, but it will give a warning. Enum specifications can include delimiters, and is the only time "<>"s are contained in other "<>"s:
sscanf("1 12.0 Bob,c", "e<ifp<,>sc>", var);
Note that the delimiter will remain in effect after the enum is complete. You can even use ">" as a specifier by doing "p<\>>" (or the older "p>").
When used with strings, the collection behaviour is overruled. Most specifiers are still space delimited, so for example this will work:
sscanf("1 2 3", "p<;>iii", var0, var1, var2);
Despite the fact that there are no ";"s. However, strings will ONLY use the specified delimiters, so:
sscanf("hello 1", "p<->si", str, var);
Will NOT work - the variable "str" will contain "hello 1". On the other hand, the example from earlier, slightly modified:
sscanf("hello there>27", "p<>>si", str, var);
WILL work and will give an output of:
hello there
27
You can now have optional delimiters using "P" (upper case "p" to match other "optional" specifiers). These are optional in the sense that you specify multiple delimiters and any one of them can be used to end the next symbol:
sscanf("(4, 5, 6, 7)", "P<(),>{s}iiii", a, b, c, d);
This uses a "quiet section" to ignore anything before the first "(", and then uses multiple delimiters to end all the text. Example:
sscanf("42, 43; 44@", "P<,;@>a<i>", arr);
? ?
EVERY format specifier (that is, everything except '', {} and p) now has an optional equivalent - this is just their letter capitalised, so for example the old "z" optional string specifier is now "S" (there is still "z" and, for completeness, "Z", but both give warnings). In addition to optional specifiers, there are also now default values:
sscanf("", "I(12)", var);
The "()"s (round brackets) contain the default value for the optional integer and, as the main string has no data, the value of "var" becomes "12". Default values come before array sizes and after specifications, so an optional array would look like:
sscanf("1 2", "A<i>(3)", arr);
Note that the size of the array is "4" and the default value is "3". There are also two values which are defined, so the final value of "arr" is:
1, 2, 3, 3
Array default values are clever, the final value of:
sscanf("", "A<i>(3,6)", arr);
Will be:
3, 6, 9, 12
The difference between "3" and "6" is "3", so the values increase by that every index. Note that it is not very clever, so:
sscanf("", "A<i>(1,2,2)", arr);
Will produce:
1, 2, 2, 2
The difference between "2" and "2" (the last 2 numbers in the default) is 0, so there will be no further increase. For "l" (logical) arrays, the value is always the same as the last value, as it is with "g" if the last value is one of the special values (INFINITY, NEG_INFINITY (same as -INFINITY), NAN or NAN_E). Note that:
sscanf("", "a<I>(1,2,2)", arr);
Is invalid syntax, the "A" must be the capital part.
Enums can also be optional:
sscanf("4", "E<ifsc>(1, 12.0, Bob, c)", var);
In that code all values except "4" will be default. Also, again, you can escape commas with "\\" in default enum strings. Some final examples:
sscanf("1", "I(2)I(3)I(4)", var0, var1, var2);
sscanf("", "O(045)H(0xF4)B(0b0100)U(Y_Less)", octnum, hexnum, binnum, user);
sscanf("0xFF", "N(0b101)");
That last example is of a specifier not too well described yet - the "number" specifier, which will work out the format of the number from the leading characters (0x, 0b, 0 or nothing). Also note that the second example has changed - see the next section.
? ?
The "u", "q", and "r" specifiers search for a user by name or ID. The method of this search has changed in the latest versions of "sscanf".
Additionally "U", "Q", and "R" used to take a name or ID as their default value - this has since been changed to JUST a number, and sscanf will not try and determine if this number is online:
Previous:
sscanf(params, "U(Y_Less)", id);
if (id == INVALID_PLAYER_ID)
{
? ?// Y_Less or the entered player is not connected.
}
New:
sscanf(params, "U(-1)", id);
if (id == -1)
{
? ?// No player was entered.
}
else if (id == INVALID_PLAYER_ID)
? ?// Entered player is not connected.
}
See the section on options for more details.
Users can now optionally return an ARRAY of users instead of just one. This array is just a list of matched IDs, followed by "INVALID_PLAYER_ID". Given the following players:
0) Y_Less
1) [CLAN]Y_Less
2) Jake
3) Alex
4) Hass
This code:
new ids, i;
if (sscanf("Le", "?<MATCH_NAME_PARTIAL=1>u", ids)) printf("Error in input");
for (i = 0; ids != INVALID_PLAYER_ID; )
{
? ?if (ids == cellmin)
? ?{
? ? ? ?printf("Too many matches");
? ? ? ?break;
? ?}
? ?printf("id = %d", ids);
}
if (i == 0) printf("No matching players found.");
Will output:
id = 0
id = 1
Too many matches
Searching "Les" instead will give:
id = 0
id = 1
And searching without "MATCH_NAME_PARTIAL" will give:
No matching players found.
Basically, if an array of size "N" is passed, this code will return the first N-1 results. If there are less than "N" players whose name matches the given name then that many players will be returned and the next slot will be "INVALID_PLAYER_ID" to indicate the end of the list. On the other hand if there are MORE than "N - 1" players whose name matches the given pattern, then the last slot will be "cellmin" to indicate this fact.
When combined with "U" and returning the default, the first slot is always exactly the default value (even if that's not a valid connected player) and the next slot is always "INVALID_PLAYER_ID".
Note also that user arrays can't be combined with normal arrays or enums, but normal single-return user specifiers still can be.
? ?
The latest version of sscanf adds a new "k" specifier to allow you to define your own specifers in PAWN:
SSCANF:playerstate(string[])
{
? ?if ('0' <= string <= '9')
? ?{
? ? ? ?new
? ? ? ? ? ?ret = strval(string);
? ? ? ?if (0 <= ret <= 9)
? ? ? ?{
? ? ? ? ? ?return ret;
? ? ? ?}
? ?}
? ?else if (!strcmp(string, "PLAYER_STATE_NONE")) return 0;
? ?else if (!strcmp(string, "PLAYER_STATE_ONFOOT")) return 1;
? ?else if (!strcmp(string, "PLAYER_STATE_DRIVER")) return 2;
? ?else if (!strcmp(string, "PLAYER_STATE_PASSENGER")) return 3;
? ?else if (!strcmp(string, "PLAYER_STATE_WASTED")) return 7;
? ?else if (!strcmp(string, "PLAYER_STATE_SPAWNED")) return 8;
? ?else if (!strcmp(string, "PLAYER_STATE_SPECTATING")) return 9;
}
The code above, when added to the top level of your mode, will add the "playerstate" specifier, allowing you to do:
sscanf(params, "uk<playerstate>", playerid, state);
This system supports optional custom specifiers with no additional PAWN code:
sscanf(params, "uK<playerstate>(PLAYER_STATE_NONE)", playerid, state);
The new version of "sscanf2.inc" includes functions for "k<weapon>" and "k<vehicle>" allowing you to enter either the ID or name and get the ID back, but both are VERY basic at the moment and I expect other people will improve on them.
Note that custom specifiers are not supported in either arrays or enumerations.
Note also that custom specifiers always take a string input and always return a number, but this can be a Float, bool, or any other single cell tag type.
The optional kustom specifier "K" takes a default value that is NOT (as of sscanf 2.8) parsed by the given callback:
K<vehicle>(999)
"999" is NOT a valid vehicle model, but if no other value is supplied then 999 will be returned, allowing you to differentiate between the user entering an invalid vehicle and not entering anything at all.
Also as of sscanf 2.8, "k" can be used in both arrays and enums.
Options
The latest version of sscanf introduces several options that can be used to customise the way in which sscanf operates. There are two ways of setting these options - globally and locally:
SSCANF_Option(SSCANF_QUIET, 1);
This sets the "SSCANF_QUIET" option globally. Every time "sscanf" is called the option (see below) will be in effect. Note that the use of:
SSCANF_QUIET
Instead of a string as:
SSCANF_QUIET
Is entirely valid here - all the options are defined in the sscanf2 include already.
Alternatively you can use "?" to specify an option locally - i.e. only for the current sscanf call:
sscanf(params, "si", str, num);
sscanf(params, "?<SSCANF_QUIET=1>si", str, num);
sscanf(params, "si", str, num);
Obviously "s" without a length is deprecated, and the first and last "sscanf" calls will give a warning in the console, but the second one won't as for just that one call prints have been disabled. The following code disables prints globally then enables them locally:
SSCANF_Option(SSCANF_QUIET, 1);
sscanf(params, "si", str, num);
sscanf(params, "?<SSCANF_QUIET=0>si", str, num);
sscanf(params, "si", str, num);
Note that disabling prints is a VERY bad idea when developing code as you open yourself up to unreported buffer overflows when no length is specified on strings less than 32 cells (the default length).
To specify multiple options requires multiple calls:
SSCANF_Option(SSCANF_QUIET, 1);
SSCANF_Option(MATCH_NAME_PARTIAL, 0);
sscanf(params, "?<SSCANF_QUIET=1>?<MATCH_NAME_PARTIAL=0>si", str, num);
The options are:
? ?
? ?The behaviour of "U", "Q", and "R" have been changed to take any number as a default, instead of a connected player. Setting "OLD_DEFAULT_NAME" to "1" will revert to the old version.
? ?
? ?Currently sscanf will search for players by name, and will ALWAYS search for player whose name STARTS with the specified string. If you have, say "[CLAN]Y_Less" connected and someone types "Y_Less", sscanf will not find "[CLAN]Y_Less" because there name doesn't start with the specified name. This option, when set to 1, will search ANYWHERE in the player's name for the given string.
? ?
? ?Whatever the value of "MATCH_NAME_PARTIAL", the first found player will always be returned, so if you do a search for "_" on an RP server, you could get almost anyone. To detect this case, if more than one player will match the specified string then sscanf will return an ID of "cellmin" instead. This can be combined with "U" for a lot more power:
? ?
? ?sscanf(params, "?<CELLMIN_ON_MATCHES=1>U(-1)", id);
? ?if (id == -1)
? ?{
? ? ? ?// No player was entered.
? ?}
? ?else if (id == cellmin)
? ?{
? ? ? ?// Multiple matches found
? ?}
? ?else if (id == INVALID_PLAYER_ID)
? ?{
? ? ? ?// Entered player is not connected.
? ?}
? ?else
? ?{
? ? ? ?// Found just one player.
? ?}
? ?
? ?
? ?Don't print any errors to the console. REALLY not recommended unless you KNOW your code is stable and in production.
? ?
? ?As with "U", "K" used to require a valid identifier as the default and would parse it using the specified callback, so this would NOT work:
? ?
? ?K<vehicle>(Veyron)
? ?
? ?Because that is not a valid vehicle name in GTA. The new version now JUST takes a number and returns that regardless:
? ?[code
? ?K<vehicle>(9999)
? ?
? ?This setting reverts to the old behaviour.
All specifiers
For quick reference, here is a list of ALL the specifiers and their use:
[b][u]Format[/u][/b] [b][u]Use[/u][/b]
L(true/false) Optional logical truthity
l Logical truthity
K<callback>(any format number) ? ? ? ?Optional custom operator
k<callback> Custom operator
B(binary) Optional binary number
b Binary number
N(any format number) Optional number
n Number
C(character) Optional character
c Character
I(integer) Optional integer
i Integer
D(integer) Optional integer
d Integer
H(hex value) Optional hex number
h Hex number
O(octal value) Optional octal value
o Octal value
F(float) Optional floating point number
f Floating point number
G(float/INFINITY/-INFINITY/NAN/NAN_E) Optional float with IEEE definitions
g Float with IEEE definitions
{ Open quiet section
} Close quiet section
P<delimiters> Multiple delimiters change
p<delimiter> Delimiter change
Z(string)[length] Invalid optional string
z(string)[length] Deprecated optional string
S(string)[length] Optional string
s[length] String
U(any format number) Optional user (bot/player)
u User (bot/player)
Q(any format number) Optional bot (bot)
q Bot (bot)
R(any format number) Optional player (player)
r Player (player)
A<type>(default)[length] Optional array of given type
a<type>[length] Array of given type
E<specification>(default) Optional enumeration of given layout
e<specification> Enumeration of given layout
'string' Search string
% Deprecated optional specifier prefix
? Local options specifier
"extract"
I've written some (extendable) macros so you can do:
extract params -> new a, string:b, Float:c; else
{
? ?return SendClientMessage(playerid, COLOUR_RED, "FAIL!");
}
This will compile as:
new a, string:b, Float:c;
if (unformat(params, "isf", a, b, c))
{
? ?return SendClientMessage(playerid, COLOUR_RED, "FAIL!");
}
Note that "unformat" is the same as "sscanf", also note that the "SendClientMessage" part is optional:
extract params -> new a, string:b, Float:c;
Will simply compile as:
new a, string:b, Float:c;
unformat(params, "isf", a, b, c);
Basically it just simplifies sscanf a little bit (IMHO). I like new operators and syntax, hence this, examples:
// An int and a float.
extract params -> new a, Float:b;
// An int and an OPTIONAL float.
extract params -> new a, Float:b = 7.0;
// An int and a string.
extract params -> new a, string:s;
// An int and a playerid.
extract params -> new a, player:b;
As I say, the syntax is extendable, so to add hex numbers you would do:
#define hex_EXTRO:%0##%1,%2|||%3=%9|||%4,%5) EXTRY:%0##%1H"("#%9")"#,%2,%3|||%4|||%5)
#define hex_EXTRN:%0##%1,%2|||%3|||%4,%5) EXTRY:%0##%1h,%2,%3|||%4|||%5)
#define hex_EXTRW:%0##%1,%2|||%3|||%4,%5) EXTRY:%0##%1a<h>,%2,%3|||%4|||%5)
That will add the tag "hex" to the system. Yes, the lines look complicated (because they are), but the ONLY things you need to change are the name before the underscore and the letter near the middle ("H", "h" and "a<h>" in the examples above for "optional", "required" and "required array" (no optional arrays yet besides strings)).
New examples (with "hex" added):
// A hex number and a player.
extract params -> new hex:a, player:b;
// 32 numbers then 32 players.
extract params -> new a, player:b;
// 11 floats, an optional string, then an optional hex number.
extract params -> new Float:f, string:s = "optional", hex:end = 0xFF;
The code is actually surprisingly simple (I developed another new technique to simplify my "tag" macros and it paid off big style here). By default "Float", "string", "player" and "_" (i.e. no tag) are supported, and their individual letter definitions take up the majority of the code as demonstrated with the "hex" addition above. Note that "string:" is now used extensively in my code to differentiate from tagless arrays in cases like this, it is removed automatically but "player:" and "hex:" are not so you may wish to add:
#define player:
#define hex:
To avoid tag mismatch warnings (to remove them AFTER the compiler has used them to determine the correct specifier).
The very first example had an "else", this will turn:
unformat(params, "ii", a, b);
In to:
if (unformat(params, "ii", a, b))
You MUST put the "else" on the same line as "extract" for it to be detected, but then you can use normal single or multi-line statements. This is to cover common command use cases, you can even leave things on the same line:
else return SendClientMessage(playerid, 0xFF0000AA, "Usage: /cmd <whatever>");
There is now the ability to split by things other than space (i.e. adds "P<?>" to the syntax - updated from using "p" to "P"):
extract params<|> -> new a, string:b, Float:c;
Will simply compile as:
new a, string:b, Float:c;
unformat(params, "P<|>isf", a, b, c);
Note that for technical reasons you can use "<->" (because it looks like the arrow after the "extract" keyword). You also can't use "<;>", "<,>", or "<)>" because of a bug with "#", but you can use any other character (most notably "<|>", as is popular with SQL scripts). I'm thinking of adding enums and existing variables (currently you HAVE to declare new variables), but not right now.
Errors/Warnings
? ?
If you get this error, DO NOT just download the dll from a random website. This is part of the "Microsoft Visual Studio Redistributable Package". This is required for many programs, but they often come with it. Download it here:
http://www.microsoft.com/download/en...s.aspx?id=5555
? ?
If you get this error, you need to make sure that you have recompiled ALL your scripts using the LATEST version of "sscanf2.inc". Older versions didn't really require this as they only had two natives - "sscanf" and "unformat", the new version has some other functions - you don't need to worry about them, but you must use "sscanf2.inc" so that they are correctly called. If you think you have done this and STILL get the error then try again - make sure you are using the correct version of PAWNO for example.
? ?
This error comes up when people try and put too much data in to a string. For example:
new str;
sscanf("Hello there, how are you?", "s", str);
That code will try and put the string "Hello there, how are you?" in to the variable called "str". However, "str" is only 10 cells big and can thus only hold the string "Hello ther" (with a NULL terminator). In this case, the rest of the data is ignored - which could be good or bad:
new str, num;
sscanf("Hello there you|42", "p<|>si", str, num);
In this case "num" is still correctly set to "42", but the warning is given for lost data ("e you").
Currently there is nothing you can do about this from a programming side (you can't even detect it - that is a problem I intend to address), as long as you specify how much data a user should enter this will simply discard the excess, or make the destination variable large enough to handle all cases.
A specifier such as:
a<I(5)>[10]
Has been written - here indicating an array of optional integers all with the default value "5". Instead you should use:
A<i>(5)[10]
This is an optional array of integers all with the default value "5", the advantage of this is that arrays can have multiple defaults:
A<i>(5, 6)[10]
That will set the array to "5, 6, 7, 8, 9, 10, 11, 12, 13, 14" by default, incrementing by the found difference each time.
Similar to the previous warning, A specifier such as:
e<I(5)f>
Is invalid, instead use:
E<if>(42, 11.0)
This forces ALL the parts of an enum to be optional - anything less is not possible.
? ?
This is not allowed:
sscanf(params, "a<a<i>>", arr);
A work-around can be done using:
sscanf(params, "a<i>", arr);
That will correctly set up the pointers for the system.
? ?
This is not allowed (see the section on search strings):
a<'hello'i>[10]
? ?
This is not allowed:
a<p<,>i>[10]
Instead use:
p<,>a<i>[10]
? ?
This is not allowed:
a<{i}>[10]
Instead use:
{a<i>[10]}
? ?
The given specifier is not known (this post contains a full list of all the specifiers near the bottom).
You used "Z", don't; instead use "S".
? ?
You used "z", don't; instead use "S".
? ?
An optional specifier has been set as (for example):
I()
Instead of:
I(42)
This does not apply to strings as they can be legitimately empty.
? ?
You have a default value on an optional specifier that looks like:
I(42
Instead of:
I(42)
? ?
You have no default value on an optional specifier:
I
Instead of:
I(42)
A custom delimiter of:
p<
Was found with no matching ">" after one character. In this case the system assumes you are using the old (deprecated) style of delimiters and sets it to just "<". Instead use:
p<,>
Or, if you really do want a delimiter of "<" then use:
p<<>
Note that this does not need to be escaped; however, a delimiter of ">" does:
p<\>>
The "\" may also need to be escaped when writing actual PAWN strings, leading to:
p<\\>>
This also applies to array types ("a<" vs "a<i>"), note that this will result in an invalid array type.
You are using the old style:
p,
Instead of:
p<,>
This also applies to array types ("ai" vs "a<i>").
The format specifier just ends with:
p
This also applies to array types ("a" vs "a<i>").
A string has been written as:
s[10
Instead of:
s[10]
I.e. the length has not been closed.
A string has been written as:
s
Instead of:
s[10]
I.e. the length has not been included.
? ?
An invalid array or string size has been specified (0, negative, or not a number).
? ?
A string or array has been given a length that is not a number.
? ?
In the old system, strings were not required to have lengths but this introduced security problems with overflows. Now you must add a length or get the default of "32".
? ?
Arrays are newer than strings, so never had an implementation not requiring a length, so there is no compatability problems in REQUIRING a length to be given.
? ?
You have tried writing something like this:
{i{x}}
This has a quiet section ("{}") inside another one, which makes no sense.
? ?
"}" was found with no corresponding "{":
i}
? ?
This is caused by specifiers such as:
{fe<i}x>
Where the quiet section is started before the enum, but finishes part way through it rather than after it. This can be emulated by:
{f}e<{i}x>
? ?
Basically, you can't do:
e<fa<i>[5]f>
You can, however, still do:
e<fiiiiif>
This is a little more awkward, but is actually more technically correct given how enums are compiled.
? ?
A specifier starts a string with "'", but doesn't close it:
i'hello
"format" uses code such as "%d", sscanf only needs "d", and confusingly the C equivalent function (also called "sscanf") DOES require "%". Sorry.
Default values for arrays can be partially specified and the remainder will be inferred from the pattern of the last two:
A<i>(0, 1)[10]
That specifier will default to the numbers "0" to "9". However, because enums have a mixture of types, all the default values for "E" must ALWAYS be specified:
E<iiff>(0, 1, 0.0, 1.0)
This will not do:
E<iiff>(0, 1)
The "?" specifier for local options must appear outside any other specifier.
? ?
An option was specified with no value:
?<OLD_DEFAULT_NAME>
? ?
The given option was not recognised. Check spelling and case:
?<NOT_A_VALID_NAME=1>
A "k" specifier has been used, but the corresponding function could not be found. If you think it is there check the spelling matches exactly - including the case.
You edited something in the sscanf2 include - undo it or redownload it.
Changelog
sscanf 2.8.2 - 18/04/2015
- Fixed a bug where "u" wasn't working correctly after a server restart.