2.0.4 Release Candidate 2

[DevUrandom]

Release Candidate 2 for our 2.0.4 release has just been uploaded.

Installers for Windows and Linux as well as the sourcecode can be found on the downloads page

Changes since rc1:

• MacOS support!
• Scripting engine now supports functions incl. local variables
• Some more bugfixes

A complete list of changes can be found in the ChangeLog.

------

Addition:
We changed our forums software to the SMF.
All useraccounts and posts are still ok

Whats new: The forum accounts are linked with our Wiki now.

[rajasta]

There's a missing semicolon in line 2368 in lib/script/script_parser.y causing the build to break.

In contrast to RC1, there are a lot of error messages while playing:

error: resetLocalVars: wrong event index: 30
error: interpRunScript: could not reset local vars for event 30
error: interpRunScript: *** ERROR EXIT *** (CurEvent=30)
error: Error in Warzone: file event.c, function eventFireCallbackTrigger, line 988
error: eventFireCallbackTrigger: trigger 30 (CALL_STRUCT_ATTACKED): code failed

error: Error in Warzone: file stack.c, function stackReset, line 558
error: stackReset: stack is not empty
error: resetLocalVars: wrong event index: 30
error: interpRunScript: could not reset local vars for event 30
error: interpRunScript: *** ERROR EXIT *** (CurEvent=30)

Other than that, builds and runs fine

Cheers,
-sascha

[DevUrandom]

That "local vars" in the error messages remind me of the newly added function (with local vars) support for the scripting engine... Troman!! *me goes to chase a dev*

For the script_parser.y: That could be of the same source. Even though I wonder why it builds fine here...

[DevUrandom]

We tried to find your problem with the missing semicolon, but couldn't.
Could you please provide the exact error message from your compiler, telling you about the missing semicolon?
And additionally an excerpt from script_parser.y containing the line with the missing semicolon and the parts around it?

Please also provide information about the compiler you used and the versions of Bison and Flex.

[Troman]

rajasta, there are 2 error messages and they all refere to the same script event. Can you tell us what map you were playing, but what is more importand what Tech Level? Was it a campaign mode or skirmish?

[rajasta]

Error message while building:

Making all in script
bison -y -oy.tab.c -d script_parser.y
script_parser.y:2369.11: parse error, unexpected ":", expecting ";" or "|"
script_parser.y:2374.6-2375.31: $1 of `argument_decl' has no declared type
script_parser.y:2374.6-2375.35: invalid $ value
script_parser.y:2374.6-2375.35: $7 of `argument_decl' has no declared type
...and subsequent errors...

Excerpt vom script_parser.y:

argument_decl:  '(' ')'
        {
        /* remember that local var declaration is over */
                localVariableDef = FALSE;
                debug( LOG_SCRIPT, "localVariableDef = FALSE 6");
        }
        ;    bDeclared = TRUE;
        }

This all on FreeBSD 6.1-STABLE with GCC 3.4.4, GNU bison 1.75 and flex 2.5.4.

The script errors occur in the Fastplay tutorial, and seemingly in any campaign level (playing Alpha 7 right now).

Cheers,
-sascha

[DevUrandom]

Could you try to use Bison 2(.1) ?
I am using that on Windows and had no problems.

[Troman]

rajasta, there's really something wrong with your Bison. argument_decl doesn't have to have a type, because nothing is assigned to it (if you look at rule: argument_decl: '(' ')' )

The line with event_decl:    event_subdecl ';' has correct Bison syntax as well.

Try to use a different Bison version. For me Bison 2.1 didn't work, i'm using 1.875, but you can try if 2.1 will work for you.

Script errors are probably the result of compilation errors.

[rajasta]

rajasta, there's really something wrong with your Bison. argument_decl doesn't have to have a type, because nothing is assigned to it (if you look at rule: argument_decl: '(' ')' )

The line with event_decl:    event_subdecl ';' has correct Bison syntax as well.

Try to use a different Bison version. For me Bison 2.1 didn't work, i'm using 1.875, but you can try if 2.1 will work for you.

Script errors are probably the result of compilation errors.

Just did a fresh build with Bison 2.1, which works well. Script errors still there, though.

error:      Error in Warzone: file event.c, function eventFireCallbackTrigger, line 988
error:      eventFireCallbackTrigger: trigger 27 (CALL_NEWDROID): code failed

error:      Error in Warzone: file stack.c, function stackReset, line 558
error:      stackReset: stack is not empty
error:      resetLocalVars: wrong event index: 27
error:      interpRunScript: could not reset local vars for event 27
error:      interpRunScript: *** ERROR EXIT *** (CurEvent=27)

Cheers,
-sascha

[DevUrandom]

Those errors will not appear in final 2.0.4 anymore.