Thu, 26 May 2016 15:00:20 +0100Add support for functions returning VOID (i.e. non-standard extension, allowing functions that do not return any data)
mjsousa [Thu, 26 May 2016 15:00:20 +0100] rev 1016
Add support for functions returning VOID (i.e. non-standard extension, allowing functions that do not return any data)

Thu, 26 May 2016 14:26:33 +0100Add -warn flag when running flex -> warn of potential bugs
mjsousa [Thu, 26 May 2016 14:26:33 +0100] rev 1015
Add -warn flag when running flex -> warn of potential bugs

Fri, 13 May 2016 12:18:50 +0100Add support for non-standard VOID datatype. May ony be used to define functions returning VOID.
mjsousa [Fri, 13 May 2016 12:18:50 +0100] rev 1014
Add support for non-standard VOID datatype. May ony be used to define functions returning VOID.

Wed, 11 May 2016 19:38:31 +0100Delete the YY_NO_UNPUT define, as we do use the unput() function.
mjsousa [Wed, 11 May 2016 19:38:31 +0100] rev 1013
Delete the YY_NO_UNPUT define, as we do use the unput() function.

Wed, 11 May 2016 18:41:45 +0100Add support for non standard feature: allow POUs with no in, out and inout parameters
mjsousa [Wed, 11 May 2016 18:41:45 +0100] rev 1012
Add support for non standard feature: allow POUs with no in, out and inout parameters

Sun, 08 May 2016 20:01:15 +0100Add option to not add the EN and ENO parameters to every function and FB (generated C code becomes smaller, and uses less memory for function invocations)
mjsousa [Sun, 08 May 2016 20:01:15 +0100] rev 1011
Add option to not add the EN and ENO parameters to every function and FB (generated C code becomes smaller, and uses less memory for function invocations)

Sat, 07 May 2016 21:17:49 +0100Correctly identify errors when parsing erroneous code (make sure flex goes back to INITIAL state when code contains errors that do not allow determining whether ST or IL is being parsed)
mjsousa [Sat, 07 May 2016 21:17:49 +0100] rev 1010
Correctly identify errors when parsing erroneous code (make sure flex goes back to INITIAL state when code contains errors that do not allow determining whether ST or IL is being parsed)

Tue, 28 Jun 2016 13:34:29 +0000Created new branch fix_compilation_warnings fix_compilation_warnings
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Tue, 28 Jun 2016 13:34:29 +0000] rev 1009
Created new branch fix_compilation_warnings

Fri, 06 May 2016 11:48:02 +0300fix compilation error about missing braces
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Fri, 06 May 2016 11:48:02 +0300] rev 1008
fix compilation error about missing braces

IEC_TIMESPEC has two fields tv_sec and tv_nsec.

Compilation error:
./build/POUS.c:600:45: error: missing braces around initializer [-Werror=missing-braces]
static const STEP temp_step = {{0, 0}, 0, {0, 0}};
^
compilation terminated due to -Wfatal-errors.

Fri, 06 May 2016 11:38:35 +0300fix warning about overflow if matiec is running on 64-bit platform,
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Fri, 06 May 2016 11:38:35 +0300] rev 1007
fix warning about overflow if matiec is running on 64-bit platform,
but the generated C code will cross-compiled for 32-bit platform

For example:
./build/config.c:29:39: error: large integer implicitly truncated to unsigned type [-Werror=overflow]
unsigned long greatest_tick_count__ = 18446744073709551611UL; /*tick*/
^
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors