Move standard FBs to a pre-converted C file, insted of converting them every time along with the IEC source.

Move library files compiled to C to their own subdiectory.

Fix stupid mistake in previous commit (use 'long double' instead of 'ld' in istandard library macro)

merge

Update build/compile instructions to reflect the fact that autoconf needs to be executed.

Fix time conversion function in std library, and change into macro (so it may be used in variable initialisations)

Add support for the stepname.T syntax.

Change the name of the variable with the step state to stepname.X (in the generated VARIABLES.csv file)

Add support for Stepname.X syntax.

Remove dead code previously left in by mistake.

Add error message for invalid datatype of transition condition. Generalize datatype narrowing algorithm for transition conditions.

merge

closed temporary fix branch

Check VAR_EXTERN variables declared in FBs instantiated in a Program (and recursively too - FBs in FBs).

Fix typo in as yet dormant code (related to REF_TO keyword, that is not yet active)

Fix compilation error on platforms where real64_t is mapped onto 'long double'

Correctly handle structured variables that include FB and external FBs (example: FB1.FB2.extFB3.FB4.extFB5.extFB6.structvar.field1 := 42;) (this commit fixes only ST code. TODO: IL and SFC)

Remove call to type_is_complex() in ST code generation.

A little code cleanup (reduce number of possible variable generation states)

Finish: Change order of SET_xxx() macros. (this will allow me to simplify the print_setter() methods later on)

Change order of SET_xxx() macros. (this will allow me to simplify the print_setter() methods later on)

More static declarations in POUS.c in order to avoid conflicting symbol definitions with new POUS.c inclusion scheme

Fix multiple resources support, POUS.c now only contain static definitions. POUS.c is included in configuration C code as well as in resources to allow GLOBAL FBs to be declared in configurations

Disable stage4 options with on windows since getsuboptr isn't supported in mingw

merge

Track of line number correctly when input file has code with very long lines.

Fix memory leak in lexical parser.

Make generation of #line directives optional.

Insert #line directives in generated C code.

Add support for parsing of REF_TO keyword (defined in IEC61131-3 v3). This support is currently inactive (in flex) until we get to add C code generation later on.

Update files to be ignored by mercurial: ignore files generated by autoconf, directory test/, and *.orig

Fix bug: do not print IL 'label' when generating inline functions (JMPxx label was generating erroneous C code)

Add limited support for the REF() operator (defined in v3 of IEC 61131-3)

Remove assertion being failed by IL labels (IL labels do not yet have specific datatypes).

Added stage1_2/Makefile.am weird rule to keep compatible with previous version of automake

Merge

fix definition of pragma.

Fix the state machine that became broken 2 commits ago (when adding support for nested comments)

Add option to control support for nested comments (default is off, as defined in IEC 61131-3 v2)

Add support for nested comments

Fix bug: when checking compatibility between GLOBAL and EXTERNAL variables, must only enforce GLOBAL CONSTANT => EXTERNAL CONSTANT.
Reverse CONSTANT implication is not enforced, and neither is RETAIN compatibility.

merge

Fix bug: correctly generate code when accessing external variables declared inside FBs as a structured variable (realvar := fb1.fb2.extvar1.realvar)

Fix bug in standard: standard does not allow multiple VAR_GLOBAL ... END_VAR constructs in configurations and resources. This is probably a bug, so we allow it.

Code cleanup (part 3): generate_c_typedecl_c is no longer needed for code generation in POUS.c It is now only needed for datatype declaration in POUS.h

Code cleanup (part 2): generate_typedecl_c now only prints to POUS.h !

Code cleanup (part 1): subrange check functions are now declared in POUS.h (as static inline functions or #define)

Fix get_datatype_info_c::is_subrange(), which did not work when using base type! (we now use get_equivtype() instead of get_base_type() )

fix a couple of typos.

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.