iec-checker
iec-checker copied to clipboard
jubnzv
Static analysis of IEC 61131-3 programs
Hi jubnzv, your 'dead-code.st' gives me an unexpected result on windows. Expected result for 'dead-code.st': ``` Report for test/st/[dead-code.st](http://dead-code.st/): Report for test/st/dead-code.st:[PLCOPEN-L17] 17:6 Each IF instruction should have an ELSE...
The current implementation of the test suite in Python seems too complicated. It could be rewritten in OCaml using cram tests and alcotest/ounit2.
We should set maximum supported versions of dependencies in `dune-project` to avoid backward compatibilities problems in the future.
The following snippet raises false positive for CP1: ``` PROGRAM l10 VAR END_VAR %MW10.2.4.1 := 42; (* False positive PLCOPEN-CP1 *) END_PROGRAM ``` Actually, this warning should be reported only...
The use of hardcoded physical addresses should be avoided. So, we have to report any physical address in the code, except those that are used when initializing variables: ``` PROGRAM...
We should use automated release generation for the project for Linux and Windows. The most challenging step here is Windows support. Currently, I use [a Cygwin-based OCaml environment](https://ocaml.org/docs/ocaml-on-windows), that contains...