Hi,
I´m currently translating my old A7 .wdl scripts to the new Lite-C for A8.
I´m being able to update most of my .wdl code to Lite-C so far, but bumped into a tricky one now:

it´s generating the following error message:

ERROR in items.c, line 181:
'temp' undeclared identifier"
< vec_set (temp.x, my .x);
>

Way tricky to find the replacement syntax, because the code in the examples is the same i´m using. Is 'temp' replaced by another syntax, or the ´temp´ concept isn´t used anymore in the new codes?
Thanks in advance.

"temp.x" is a vector, before using any vector, you need yo declare it.
Example:
VECTOR temp;

You are right, temp is not used in lite-c, you have to declare it by yourself.

SIGH... i think i understand, thanks guys.
To be able to still use the old code without changing it too much (at least in this first syntax translation stage), i´m declaring the 'temp' vector inside the function, in hopes it will work again... or so i tought.
After i do this, THREE simultaneous errors appear in the runtime warning:


ERROR in items.C line 216:
Cannot convert FIXED to STRUCT vector
< temp = my.skill1
>

ERROR in items.C line 217:
Can not convert 'struct vector' to 'Long'
< controlitem[temp]=1;
>

...and the third is your standard syntax-need-a-fix/everthing-is-case-sensitive-now/etc buggy code.
But for the first two errors... crap, i migt need to declare exclusive 'temps'
for each of them, probably?

This is my standard for temp to use it as I was used to when writing in C-Script:
VECTOR* temp = {x=0;y=0;z=0;}

then you have to write probably (is long ago that I used skills) something like this:
temp.x = skill1;
temp.y = skill2;
temp.z = skill3;

Don't know whether there is a more elegant way.

Nope... declaring the vector as a global var like you did still gives the same errors... but thanks anyway.
My mistake here is to have been away from coding for so long.
Those functions are all outdated, and their structural logic is probably very flawed.
Still, i´d like to make the old code run again to fix it up little by little, but it seems that i´ll already have to make essential changes to it just to get to this stage.
Many parts have been taken from other old examples, and many functions might be easily replaced by small instructions, perhaps.
Still, i´ll give the initial fix-it a go.

Well, that particular error message disappeared when i declared a new ´temp´ var inside the function itself (renamed it to be used especifically on that place only):

Now i´m have my first trouble with an ACTION function... (still couldn´t find a working ACTION Lite-C structure example).
Well, one problem at a time, i guess... thanks again, everybody.

This is probably only a naming problem:

write 'action myAction()' - with the brackets
instead of
action myAction - without brackets

"temp = my.skill1" doesn't work in lite-c, it's a lot less forgiving than c-script. you need.

vec_set(temp.x,my.skill1);


I had a problem going from c-script to lite-c as well but it's worth it as it is so much more powerful. I love being able to pass near limitless parameters. Saved hundreds of lines of code because of that.

You know that this piece of code is pointless and can be replaced by the line "controlitem[my.skill1]=1;" ?