We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
formatnumber cause an error sources\lib/formatnumber.inc(115) : error 020: invalid symbol name "" related with this string:
formatnumber
sources\lib/formatnumber.inc(115) : error 020: invalid symbol name ""
else if ( iTag == tagof( hex: ) || iTag == tagof( Hex: ) )
But I use some other version of sscanf2.inc where this bug is fixed:
#define hex:%0;unformat(_:EXTRZ:EXTRX:%1); %0;unformat(_:EXTRZ:EXTRX:%1);
And I'm pretty sure what this changes was made not by me. So, I we can made this changes without any fears of incompatibility or not?
The text was updated successfully, but these errors were encountered:
7504f7b
I had to slightly change that fix, as it only worked with certain invocations of the extract macro. It also shouldn't break compatibility.
Also that formatnumber include seems to crash the default PAWN compiler, had to test it with Zeex' compiler fork.
Sorry, something went wrong.
Should probably do the same for the other bare tags, since they might not be used elsewhere right now, but that doesn't mean they can't be.
remove other tags in unformat context only
c939110
see #15
maddinat0r
No branches or pull requests
formatnumber
cause an errorsources\lib/formatnumber.inc(115) : error 020: invalid symbol name ""
related with this string:But I use some other version of sscanf2.inc where this bug is fixed:
And I'm pretty sure what this changes was made not by me.
So, I we can made this changes without any fears of incompatibility or not?
The text was updated successfully, but these errors were encountered: