Difference between revisions of "STATOR:Establishing code-base"

From STATOR
Jump to navigation Jump to search
Line 15: Line 15:
 
** Implementation of some program analyses may be slower then the one in programming languages like OCaml or F#. Nevertheless, it is quite difficult to predict impact of this potentially increased programming effort.
 
** Implementation of some program analyses may be slower then the one in programming languages like OCaml or F#. Nevertheless, it is quite difficult to predict impact of this potentially increased programming effort.
  
=== F# ===
+
=== F# (.NET/Mono) ===
  
 
* <b>pros</b>
 
* <b>pros</b>

Revision as of 16:46, 25 July 2014

Here we list pros and cons of all our approaches towards establishing STATOR's code-base. All pros/cons are listed in the order from the most important to the least one. We further assign for all listed pros/cons a global "importance level", which is a number in [1,...,10].

Main implementation language/platform

Java

  • pros
    • We can take a lot of code from tools like CPAchecker and Stanse with minimal effort.
    • Huge standard library
    • There several very good IDEs for development of Java applications.
    • It is stable and portable to many different platforms.
    • Many students know it.
  • cons
    • Implementation of some program analyses may be slower then the one in programming languages like OCaml or F#. Nevertheless, it is quite difficult to predict impact of this potentially increased programming effort.

F# (.NET/Mono)

  • pros
    • May provide faster implementation of some program analyses then in Java, because symbolic manipulations of particular data structures (like syntax trees, expressions, BDD,...)
    • We can take a C front end from tools like CPAchecker, Stanse, Bugst, or Predator with minimal effort. It only requires to dump internal CFG representations of the tools to disc and load them into equivalent data structures syntactically expressed in F#.
    • When we are in .NET we can freely use any other .NET language (C#, Visual basic, managed C++, ...). Since many students know C# and C# is similar to (or better then) Java, so from this point of view F# is better choice then Java. Moreover, there is also implemented integration of non-managed languages, but portability is then a question.
    • We can move to Windows and thus develop STATOR in Visual Studio. (Visual Studio can really speed-up development (e.g. excellent debugging, edit&continue, ...)
  • cons
    • Development in Mono can be less comfortable. Also support of F# in Mono known to us yet. Similarly, state of standard library is not know.
    • Portability mostly depends on qualities of Mono.
    • Not many people knows it, but the situation improves.

OCaml

  • pros
    • May provide faster implementation of some program analyses then in Java, because symbolic manipulations of particular data structures (like syntax trees, expressions, BDD,...)
    • We can take a C front end from tools like CPAchecker, Stanse, Bugst, or Predator with minimal effort. It only requires to dump internal CFG representations of the tools to disc and load them into equivalent data structures syntactically expressed in OCaml.
  • cons
    • OCaml development environments are still immature and primitive. This can slow down whole development.
    • Not many people knows it, but the situation improves.
    • OCaml is not that portable as Java.

C++

  • pros
    • a
  • cons
    • a

Preferences to features/structure of the internal program representation

pros of CPAchecker

cons of CPAchecker

pros of Stanse

cons of Stanse

pros of PAGAI

cons of PAGAI

pros of FramaC

cons of FramaC

pros of Predator

cons of Predator