Fix bug - correctly declare struct members whose type is a directly defined array (e.g.: STRUCT x: ARRAY of XXX; END_STRUCT)

Start using the called_fb_declaration annotation when generating C code from FB calls in ST.

Code cleanup: move datatype analysis to get_datatype_info_c

Fix bug-fix of previous commit.

Fix bug: allow use, as lvalues, structures/arrays inside FBs (e.g. fb1.struct1.r := 33.3).

Fix bug/issue #33 (correctly access struct/array variables declared inside a FB -> r:=FB1.FB2.struct1.array1[3] )

Add assertion suggested by Manuele.

merge

Use get_datatype_info_c::is_type_valid() to determine datatype validity
(some datatype bugs in source code were going unreported!)

Recursively check the datatype compatibility of values/expressions passed in function/FB invocations.

Change error message text so as to become more suitable to where they might occur in the source code.

Add code to check if an IN_OUT variable is being passed an IL list in formal IL FB/function invocations.

Generate correct error message when encountering IL lists embedded in IL formal invocations.

Fill in the 'datatype' anotation in the identifiers of symbolic variables.
(even though currently it is not being used).

Fix C code generation of FB invocation in IL.

Fix detection of datatype errors on IL conditional flow control operators (JMPC, RETC, ...)

Allow array_dimension_iterator to accept an array_spec_init_c.
Fixes bug activated by generating C code from IL code containing array variables.

Small code cleanup (move common code to a function)

Fix datatype analysis of conditional IL operators (CALC, CALCN, RETC, RETCN, JMPC, JMPCN, S and R)

Fix datatype analyses of S and R IL operators.

make sure all IL operands are narrowed (datatype checking algorithm)

cosmetic change only - fix code alignment.

Add support for FB call semantics of 'S' and 'R' IL operators!
Remove segfaults when analysing buggy IL code (IL operators with no operands).

Stop lvalue check from segfaulting when coming across buggy IL code (IL operator with no operand!)

Allow get_datatype_info_c to be called with NULL parameters.

Do lvalue check of function output parameters (since they may contain expressions inside array subscripts!)

Handle buggy source code gracefully (do not bork when non-array variable is used as an array. e.g: int_var[42]:= 33)

Delete debugging messages left in by mistake.

Fix segfault when doing lvalue check of buggy IEC 61131-3 source code

Fix datatype analysis of structured variables that contain arrays in their fields (e.g. var.x1[var2 + 42].y1).

Add capability of returning array subscript list while decomposing a struct/array variable.

Code cleanup: Remove unused option = Delete dead code.

merge

Declare that YYLSTYPE is not the default trivial datatype used by bison. (was causing compile errors in bison ver >= 2.7)

Fix build on Ubuntu 13.10

Fixed warning when compiling generated program containing external variable assignments

Enlarged flex buffer size in order to accept larger C pragmas

Missing braces arround extern declarartions in __SET_EXTERNAL define was making problem with GCC in switch case statements

Moved __INIT_* defines within type definition headers files

Fixed warning in accessor __SET_EXTERNAL

Fixed bug when defining task with single_data_source instead of interval_data_source

Merged Mario's changes

Fix bug related to FB invocation of FB instances declared as VAR_EXTERN.

Merged Mario's changes

Partial fix to VAR_EXTERN vs VAR_GLOBAL check. Now considers globals declared in resources too. TODO: recursively check FB declared in the program.

Allow variables declared inside resources to be referenced by res_name.var_name

Add a new node to the abstract symtax tree, which will let us do datatype checking of FB variable declarations using the standard algorithm, and no special cases.

Print filename when debugging abstract symbol table.

Consider fb_name_decl_c a non base data type class!

Fill symbol->datatype anotation for FB declarations.

Fill in the symbol.datatype annotation in symbol classes used in derived data type declarations.

Use simple_spec_init_c inside en_param_declaration_c (will reduce need to handle it as a special case in the future).

Merged

Fixed bug in string format when translating TIME and DATETIME to STRING

Fixed bug with SFC transition datatype checking

Stripped generated files again. http://stackoverflow.com/questions/3290908/which-files-generated-by-autotools-should-i-keep-in-version-control-repository

Fixed bug in case statement with enumerated type variable as case expression

Merged

Set the symbol->datatpe of function_declaration_c

Fill in the symbol->datatype of elementary datatypes.

merge

merge

Fix divide by 0 bug.

grand merge