Parse error before 'int'

[thealmightyone]

The line that the error refers to is:

int a, b, c, d, temp = 1, count = 0, x, y;

The line that is actually causing the error is the line just before, which is:

update = 0;

This call is within a procedure (these two lines are in fact the first two lines of the procedure), and the variable is a global boolean (it has to be global, as other procedures use it). I simply cannot see what is wrong.

[Meldreth]

i'd guess that update = 0; isn't immediately preceded by a type name. this works.

int update = 0;
int a, b, c, d, temp = 1, count = 0, x, y;

and this doesn't, right?

int update;
update = 0;
int a, b, c, d, temp = 1, count = 0, x, y;

in c you have to have all declarations at the start of a block. you can't mix declarations and statements like in c++.

[brewbuck]

update = 0;

is code. You can't declare variables after code.

[matsp]

In C (1989/90 standard), you are not allowed to declare new variables "after code", so if you have "update = 0; int ...", you are declaring new variables after the first "code" statement, which is not allowed.

Move the the variable declaration to the beginning of the block (blocks - anything enclosed with braces).

--
Mats

[laserlight]

The line that is actually causing the error is the line just before, which is:

What compiler are you using, and are you compiling in C90 or C99 mode? In the 1990 edition of the C standard, declarations must come before "actual" code, so this would be wrong:

update = 0;
int a, b, c, d, temp = 1, count = 0, x, y;

If this is not the problem, I suggest that you post the smallest and simplest program that demonstrates the error.

the variable is a global boolean (it has to be global, as other procedures use it)

Other functions can use the variable, or its value, if you design your functions to have appropriate parameters. Prefer local variables to global variables as it makes it easier to reason about and maintain your program.