warning 211 possibly unintended assignment

Errors List

From sa-mp wiki.

General Pawn Error List

This pages contains the most common errors and warnings produced by the pawn compiler when creating SA:MP scripts.

When the compiler finds an error in a file, it outputs a message giving, in this order:

• the name of the file
• the line number were the compiler detected the error between parentheses, directly behind the filename
• the error class (error, fatal error or warning)
• an error number
• a descriptive error message

For example:

Note: The error may be on the line ABOVE the line that is shown, since the compiler cannot always establish an error before having analyzed the complete expression.

Error categories

Errors are separated into three classes:

• Describe situations where the compiler is unable to generate appropriate code.
• Errors messages are numbered from 1 to 99.

Fatal errors

• Fatal errors describe errors from which the compiler cannot recover.
• Parsing is aborted.
• Fatal error messages are numbered from 100 to 199.
• Warnings are displayed for unintended compiler assumptions and common mistakes.
• Warning messages are numbered from 200 to 299.

Common Errors

001: expected token.

A required token is missing.

002: only a single statement (or expression) can follow each “case”

Every case in a switch statement can hold exactly one statement. To put multiple statements in a case, enclose these statements between braces (which creates a compound statement).

The above code also produces other warnings/errors:

004: function "x" is not implemented

Most often caused by a missing brace in the function above.

025: function heading differs from prototype

This usually happen when new sa-mp version comes with new addition of argument to a function, like OnPlayerGiveDamage from 0.3x to 0.3z. The scripter must add "bodypart" argument to OnPlayerGiveDamage callback on their script.

Caused by either the number of arguments or the argument name is different.

035: argument type mismatch (argument x)

An argument passed to a function is of the wrong 'type'. For example, passing a string where you should be passing an integer.

036: empty statement

Caused by a rogue semicolon ( ; ), usually inadvertently placed behind an if-statement.

046: unknown array size (variable x)

For array assignment, the size of both arrays must be explicitly defined, also if they are passed as function arguments.

047: array sizes do not match, or destination array is too small

For array assignment, the arrays on the left and the right side of the assignment operator must have the same number of dimensions. In addition:

• for multi-dimensional arrays, both arrays must have the same size;
• for single arrays with a single dimension, the array on the left side of the assignment operator must have a size that is equal or bigger than the one on the right side.

In the above code, we try to fit 12 characters in an array that can only support 8. By increasing the array size of the destination, we can solve this. Note that a string also requires a null terminator so the total length of "Hello World!" plus the null terminator is, in fact, 13.

055: start of function body without function header

This error usually indicates an erroneously placed semicolon at the end of the function header.

Common Fatal Errors

100: cannot read from file: "<file>".

The compiler cannot find, or read from, the specified file. Make sure that the file you are trying to include is in the proper directory (default: <server directory>\pawno\include).

Common Warnings

202: number of arguments does not match definition.

The description of this warning is pretty self-explanatory. You've passed either too few or too many parameters to a function. This is usually an indication that the function is used incorrectly. Refer to the documentation to figure out the correct usage of the function.

This usually happen on GetPlayerHealth function with PAWNO function auto completion as it confuses with the NPC GetPlayerHealth function that only has 'playerid' argument.

203: symbol is never used: "symbol"

You have created a variable or a function, but you're not using it. Delete the variable or function if you don't intend to use it. This warning is relatively safe to ignore.

The stock keyword will prevent this warning from being shown, as variables/functions with the stock keyword are not compiled unless they are used.

204: symbol is assigned a value that is never used: "symbol"

Similar to the previous warning. You created a variable and assigned it a value, but you're not using that value anywhere. Use the variable, or delete it. This warning, too, is relatively safe to ignore.

209: function should return a value

You have created a function without a return value

but you used it to assign on variable or function argument,

211: possibly unintended assignment

The assignment operator (=) was found in an if-statement, instead of the equality operator (==). If the assignment is intended, the expression must be wrapped in parentheses. Example:

213: tag mismatch

A tag mismatch occurs when:

• Assigning to a tagged variable a value that is untagged or that has a different tag
• The expressions on either side of a binary operator have different tags
• In a function call, passing an argument that is untagged or that has a different tag than what the function argument was defined with
• Indexing an array which requires a tagged index with no tag or a wrong tag name

Usually happen on a new variable created with missing tag on the required function such as Float:, Text3D: , Text: , etc. Example,

217: loose indentation

The compiler will issue this warning if the code indentation is 'loose', example:

Indentation means to push (indent) text along from the left of the page (by pressing the TAB key). This is common practice in programming to make code easier to read. This warning also exists to avoid dangling-else problem.

219: local variable "foo" shadows a variable at a preceding level

A local variable, i.e. a variable that is created within a function or callback, cannot have the same name as a global variable, an enum specifier, a function, or a variable declared higher up in the same function. The compiler cannot tell which variable you're trying to alter.

It is customary to prefix global variables with 'g' (e.g. gTeam ). However, global variables should be avoided where possible.

225: unreachable code

The indicated code will never run, because an instruction before (above) it causes a jump out of the function, out of a loop or elsewhere. Look for return, break, continue and goto instructions above the indicated line. Unreachable code can also be caused by an endless loop above the indicated line.

235: public function lacks forward declaration (symbol "symbol")

Your public function is missing a forward declaration.

External Links

• pawn-lang.pdf

Categories : Documentation | Scripting

Personal tools

• SA-MP Forum
• Special pages

• This page was last modified 15:42, 15 July 2016.
• Powered by BlastHack
• Privacy policy
• About SA-MP Wiki
• Disclaimers

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications You must be signed in to change notification settings

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function names are silently accepted as variables #831

Mesharsky commented Jul 14, 2022

sirdigbot commented Jul 14, 2022

Sorry, something went wrong.

peace-maker commented Jul 14, 2022

sirdigbot commented Jul 15, 2022 • edited Loading

sirdigbot commented Jul 15, 2022

Mesharsky commented Jul 15, 2022

dvander commented Jul 16, 2022

No branches or pull requests

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

Unintended assignment [closed]

I heard some programmers use if(1 == var) instead of if(var == 1) to avoid unintended assignment. Why or in what cases does it cause unintended assignment?

• 11 Because sometimes people accidentally write if (var = 1) . Personally I find (1 == var) incredibly annoying. You shouldn't be making those mistakes after writing a few programs and on the off chance you do they are usually easy to find with a debugger. –  Duck Commented Sep 22, 2012 at 0:19
• 1 btw it's called a Yoda condition. –  mvds Commented Sep 22, 2012 at 0:19
• 1 Re "Personally I find (1 == var) incredibly annoying." That's far too nice. This is an absolutely ugly construct that is completely at odds with how people think. –  David Hammen Commented Sep 22, 2012 at 1:30
• 1 Alf, perhaps it might be a good idea to assume good faith? –  pmcs Commented Sep 22, 2012 at 1:42
• 1 Asked and answered on Programmers –  user113292 Commented Sep 22, 2012 at 3:16

2 Answers 2

The problem is if you mistype the statement:

In the first case, the code after the if is executed unconditionally (with no more than a warning from the compiler, which isn't obliged to produce a warning for you — but the good ones do; if you aren't using a good compiler, get one!). In the second case, you get a syntax error at compile time, so the problem has to be fixed before the code can compile.

The problem isn't always as blatant:

never executes the code after the if , of course. Often though, you'll have:

and it won't be clear whether you intended to assign or compare. You can make it clear to the compiler and code readers (humans) by writing:

I don't use the 'back-to-front' comparison technique. I dislike the inverted conditions because they almost invariably read 'wrong' to me. I'm not comparing 1 with my variable; I'm comparing my variable with 1. So, even though logically the == operator is commutative, I don't think commutatively and prefer that 'riskier' way. I have not found myself making the assignment vs equality mistake often enough for the issue to be a problem. The compiler warns me if I do make a mistake (and I pay attention to the warning and fix the code so that there isn't a problem).

• 1 Even when my compiler didn't warn me, it still didn't take long to find. When something's always executing, it's easy to notice. It's like forgetting a break in a case label. –  chris Commented Sep 22, 2012 at 0:21
• 1 @chris you may not notice it when the if statement is not in the default code execution path. –  ouah Commented Sep 22, 2012 at 0:24
• @ouah, True, but when you test your program, you should be testing that area as well. –  chris Commented Sep 22, 2012 at 0:29
• @Jonathan, Good point, that edit with var = 0 happens too. Finding code that doesn't run when it should is a bit more tricky sometimes. –  chris Commented Sep 22, 2012 at 0:31
• Well my compiler generates C2106 for if( x = 0 ) but it doesn't if 2 vars are in question if( y = x ) –  Vinícius Commented Sep 22, 2012 at 0:54

If you mistype it as

that would cause unintended(?) assignment. Decent compilers warn about that unless you include an extra set of parentheses

to make your intention clear to the compiler.

• Annoying compilers warn about that unless you include an extra set of parentheses. –  Pete Becker Commented Sep 22, 2012 at 0:37
• Well, okay, every time I've gotten that warning so far, it was because I forgot the parentheses. But still, I'd rather the compiler warned me if some time I really didn't mean to assign. –  Daniel Fischer Commented Sep 22, 2012 at 0:42

Not the answer you're looking for? Browse other questions tagged c++ or ask your own question .

• The Overflow Blog
• At scale, anything that could fail definitely will
• Featured on Meta
• Announcing a change to the data-dump process
• Bringing clarity to status tag usage on meta sites
• What does a new user need in a homepage experience on Stack Overflow?
• Feedback requested: How do you use tag hover descriptions for curating and do...
• Staging Ground Reviewer Motivation

Hot Network Questions

• What rules of legal ethics apply to information a lawyer learns during a consultation?
• Invest smaller lump sum vs investing (larger) monthly amount
• Why is the stall speed of an aircraft a specific speed?
• Lore reasons for being faithless
• How to resolve hostname by mDNS?
• How to survive 40c while golfing
• Unable to upgrade from Ubuntu Server 22.04 to 24.04.1
• What is Zion's depth in the Matrix?
• A novel (and a movie) about a village in southern France where a strange succession of events happens
• If a Palestinian converts to Judaism, can they get Israeli citizenship?
• What would happen if the voltage dropped below one volt and the button was not hit?
• MANIFEST_UNKNOWN error: OCI index found, but Accept header does not support OCI indexes
• What other marketable uses are there for Starship if Mars colonization falls through?
• Doesn't counting hole and electron current lead to double-counting of actual current?
• How best to cut (slightly) varying size notches in long piece of trim
• Definition clarification on topology regarding closed set
• Help writing block matrix
• Find the radius of a circle given 2 of its coordinates and their angles.
• Expensive constructors. Should they exist? Should they be replaced?
• Can a quadrilateral polygon have 3 obtuse angles?
• Multiple alien species on Earth at the same time: one species destroys Earth but the other preserves a small group of humans
• Why does each state get two Senators?
• How do Trinitarian Christians defend the unfalsifiability of the Trinity?
• In roulette, is the frequency of getting long sequences of reds lower than that of shorter sequences?

• Remember me Not recommended on shared computers

Forgot your password?

Or sign in with one of these services

• Discuţii scripting

Warning 211

• warning 211: possibly unintended assignment

By PigSmo March 21, 2017 in Discuţii scripting

• Reply to this topic
• Start new topic

Recommended Posts

Salut, inainte de a imi spune problema vreau sa ma luati foarte usor pentru ca sunt foarte noob la scripturi. Incerc sa invat din greseli si de la altii. 

Bun, am vrut sa ma apuc sa fac o comanda "/updates" dar la compilare mi-au dat anumite erori! Unele dintre ele le-am rezolvat dar ultima nu o pot rezolva deloc " warning 211: possibly unintended assignment "! Nu stiu ce ar trebuii sa modific pentru a merge compilarea!

Comanda : CMD:updates(playerid, params[]) {     if(gPlayerLogged[playerid] = 0) return SendClientMessage(playerid, COLOR_YELLOW, "Nu esti conectat");     new string[128], tdialog[125], fdialog[800];     format(tdialog, sizeof(tdialog), "{FFFF00}U{FFFFFF}update-uri");     format(string, sizeof(string), "Versiune\tData - Ora\nVersiunea 0.1\t21.03.2017 - 15:30\n");     format(fdialog, sizeof(fdialog), "%s", string);     ShowPlayerDialog(playerid, DIALOG_UPDATES, DIALOG_STYLE_TABLIST_HEARDES, tdialog, fdialog, "Ok", "");     return 1;  }

Inca mai am de lucrat la ea cu alte chestii dar nu vrea sa imi compileze aceasta.

Link to comment

Share on other sites.

Acuma am terminat comanda dupa un tutorial : 

CMD:updates(playerid, params[]) {     if(gPlayerLogged[playerid] = 0) return SendClientMessage(playerid, COLOR_YELLOW, "Nu esti conectat");     new string[128], tdialog[125], fdialog[800];     format(tdialog, sizeof(tdialog), "{FFFF00}U{FFFFFF}update-uri");     format(string, sizeof(string), "Versiune\tData - Ora\nVersiunea 0.1\t21.03.2017 - 15:30\n");     format(fdialog, sizeof(fdialog), "%s", string);     ShowPlayerDialog(playerid, DIALOG_UPDATES, DIALOG_STYLE_TABLIST_HEARDES, tdialog, fdialog, "Ok", "");     return 1;  }       if(dialogid = DIALOG_UPDATES)     {         if(response)         {             if(listitem == 0)             {                 new szString[2500];                 format(szString sizeof(szString),"%s Adaugari\n", szString);                 format(szString sizeof(szString),"%s A fost adaugata comanda /bonus\n", szString);                 format(szString sizeof(szString),"%s A fost adaugata comanda /updates\n", szString);                 ShowPlayerDialog(playerid, DIALOG_STYLE_MSGBOX, "Update 0.1", szString, "Ok", "");                 return 1:                 }             }         }     }

Problema la compilare : 

C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20264) : warning 211: possibly unintended assignment C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20273) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20275) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20277) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20280) : error 021: symbol already defined: "format" C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20280) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20281) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20282) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(20284) : error 010: invalid function or declaration C:\Users\Denis\Desktop\RPG Romania 1.00.40\gamemodes\s4uriK.pwn(52151) : warning 203: symbol is never used: "szString" Pawn compiler 3.2.3664              Copyright (c) 1997-2006, ITB CompuPhase

8 Errors.  

Puteti sa-mi spuneti de ce nu merge?

if(gPlayerLogged[playerid] = 0)  

if(gPlayerLogged[playerid] == 0)  

Nu ai pus id la ultimul dialog, acel msgbox. Sintaxa pt ShowPlayerDialog (playerid,dialog_id,dialog_style,titlu,mesaj,buton1,buton2);

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

×   Pasted as rich text.    Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.    Display as a link instead

×   Your previous content has been restored.    Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

• Insert image from URL
• Submit Reply

Similar Content

Warning 215: expression has no effect.

By Divil.Scorpiono , January 28

• 3,753 views

• Divil.Scorpiono

CreatePlayerProgressBar (warning) - Ajutor scripting

By cstephan , February 15, 2023

• March 12, 2023

warning 202: number of arguments does not match definition

By staKS , November 2, 2022

• November 3, 2022

Recently Browsing    0 members

• No registered users viewing this page.
• Existing user? Sign In
• Leaderboard
• Online Users
• All Activity
• Documentation
• Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings , otherwise we'll assume you're okay to continue. For more details you can also review our Terms of Use and Privacy Policy .