opal
opal copied to clipboard
This PR adds a setup for testing alias analyses, including some (simple) test cases. More (complex) test cases alongside analyses that pass them will be added in future PR's. This...
Note: This pull request is based on #178 and should only be merged after that pull request. This pull request adds two alias analyses for the alias properties added in...
Implementation of the string analysis (the interprocedural as well as the intraprocedural variant). Original PR by PatrickN.
With Scalafmt, we can now transition to Scala 3 syntax
As suggested by https://github.com/opalj/opal/pull/187#issuecomment-1904646058 Not sure I like it though, in some places it adds additional indentation to expressions that are already indented a lot. E.g.: https://github.com/opalj/opal/blob/40e1c0adaa29e541359d0941b7782d90b1c9e40f/OPAL/br/src/main/scala/org/opalj/br/analyses/AnalysisApplication.scala#L160C1-L166C56
This seems to affect us again, maybe because of changed module-info paths: https://github.com/sbt/sbt-assembly/issues/146
https://www.opal-project.de/Hermes.html e.g. The link to "UI" and "headless mode" is not found (404) 
All of the dependencies are part of the build.sbt anyway, so can we automate this process further, by creating the .mmd file from the build.sbt on the fly?
We have an analysis that identifies Strings set as system properties, use it for, e.g., reflection analysis. This is WIP, as dependency handling and type changes (Set[String] instead of String)...