Break constant_folding_c in two classes: constant_folding_c and constant_propagation_c

Add check whether the same constant var_external variable is initialised with two (or more) different constant values.

Change algorithm for propagating VAR_GLOBAL constant values to corresponding VAR_EXTERNAL.

Disable constant propagation again (still not working correctly)

Make support for use of variables in array size declarations a command line option (off by default)

Add debug_c::print(const_value_c) for printing of const values.

Add is_undefined() method to const_value_c

Make error message more informative.

Add comments.

Add checks for use of non constant value in subranges, and lower_limit > upper_limit.

Fix previous commit (symtable operator[] must return a reference to the stored value!)

Do constant propagation of configuration/resource variables, taking into account scope of variables.

Change dsymbtable_c -> use design pattern used by C++ standard library (STL)

Change symbtable_c -> use design pattern used by C++ standard library (STL)

Remove debugging code left in by mistake.

Do constant propagation inside Configurations and Resources (required for support of extension: array [1..max] OF int); (Resources is still buggy)

Do constant folding of default initial values of datatypes.

Do constant propagation to symbolic_variables, and correctly handle constant folding and propagation of variable declarations.

When generating C code, use the const_value of a symbolic_variable when it is used in a subrange.

Small code re-organization of how const values are stored in symbol_c (can now be accessed through member functions, instead of macros)

Fix bugs introduced in previous commit (once again do constant folding of all literals in type declarations)

Do constant folding of variable's initial value (allows correct C code generation with variables in the subrange of an array declaration: ARRAY [1..max] of INT).

Delete un-used declaration.

merge

Allow variables to be used when declaring the dimension of an array.

Fix C code generation when forward references (-p command line option) is on.

Add a new pou_typename_c object to the AST to store references to previously declared Functions, FB, and Programs.

Delete unused file.

Make use of pre-parser a command line option.

Fix AST generated by parsing with preparsing switched OFF (typo in array datatypes, and fix parsing of POUs).

Fix AST generated by parsing with preparsing switched on, and allow parsing to work with preparsing off.

Fix bug introduced when adding support for relaxed datatype model: change derived_datatype_identifier_c to identifier_c when used as an identifier

Add a pre-parsing phase to stage1_2 (allows source code that references POUs and datatypes before they are declared)

Comment out unused and buggy code.

Update the comments in source code.

Fix bug introduced when adding support for relaxed datatype model. Code cleanup.

Fix main state machine in flex (states were being pushed without being poped from the stack)

merge

Make the relaxed datatype model a runtime option (off by default)

Add support for relaxed datatype model for array datatypes.

fix bug introduced a few commits ago: do not print the first char ('%') of a direct_variable_c (e.g. skip % in %IW4.2)

fix code generation when dereferencing pointers (ref_to) to arrays (ref_to_array^[5])

Fix bug: set the scope annotation in deref_operators used inside structs

Editing of error message to make it more clear.

Filling of symbol->scope annotation moved from narrow to fill_candidate_datatypes_c (became possible because narrowing of struct, array and symbolic variables is now done directly in fill_candidate_datatypes_c)

fill_candidate_datatypes_c now uses search_varinstance_decl_c instead of search_varfb_instance_type_c (moving towards deprecation of search_varfb_instance_type_c)

Do the full fill_candidate/narrow_datatype algorithm for all fields of a structured variable in the fill_candidate_datatypes_c
Allows us to remove temporary code from the search_varfb_decl_c

Fix bug with multple dereferencing (bool_var := bool_ptr_ptr^^;)

Fix bug: Add support for de-referencing pointers to struct (struct_ptr^.elem1) when used inside FB.
Note that multiple de-referencing of structs (struct_ptr_ptr^^.elem) is not supported inside FB code (this would need BIG changes to the compiler!)

Fix bug: add support for dereferencing of REF_TO to REF_TO xxx (e.g.: bool_var := ref_to_ref_to_bool^^;)

Turn support of derefencing operator '^' an option (default is not supported).

Add support for de-referencing of REF_TO datatypes (Note: dereferencing of arrays and structs not yet supported!)

Add support for REF_TO inside arrays and structs (a non-standard feature!)

Code cleanup: with the introduction of anotation_map[], generate_c_vardecl_c can now derive directly from generate_c_base_c

Fix typos in comments

Add comments, and make get_datatype_id_str_c equivalent to get_datatype_id_c

Fix calling of functions whose parameters are of an implicitly declared datatype (currently only makes sense for REF_TO datatypes, but may make sense to other datatypes too if the datatype model is changed in the future).

fix indentations.

in lvalue, add check for REF() fucntion invocation, and the NULL literal

Initialise REF_TO variables to NULL.

Make support for REF_TO ANY a command line option.

Add support for non standard REF_TO ANY (equivalent to void *)

Update some comments. (No changes to code)

Introduce absyntax class for keyword ANY, and use REF_TO(ANY) as datatype of NULL literal.

Fix bug (introduced a few commits ago) when generating SFC actions that are mapped onto variables --> Make generate_sfcdecl_c stateless (i.e. does not depend on order by which it is called).

Add support for the 'NULL' keyword, defined in version 3 of IEC 61131-3.

for option '-Op' (generate <pouname>.h/c): add '#include <pouname>.h' to the .c file, and '#ifdef <pouname>_H' to the .h file

Ass include of iec_std_lib.h in POUS.h file.

Add support for implicitly declared REF_TO datatypes.

With -Op option --> Place implicitly defined datatypes in the .h file corresponding to the POU where they are used.

Add name of POU as prefix to names of implicitly defined datatypes

Implicitly defined array datatypes use new naming method (greatly simplifies stage 4 code).

array_specification_c may be used as a datatype! Add it to spec_init_separator_c

Change REF() operator to return the correct REF_TO datatype datatype.

Narrow array subscripts correctly, even in the presence of other datatype errors (so we do not generate error messages for array subscripts that do not contain errors).

Add support for REF_TO derived datatypes (along with datatype verification)

Add option to place each POU in a distinct .c and .h file pair.

code re-organisation. Preparing for the changes to come in the next commit (one C file for each POU)

Remove un-used parameter from class constructor.

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.