redex

One of the reasons it’s hard to talk about clean C++ codebases is that there’s a huge range of possible complexity. The gap between “Solve a particular problem” and “provide a generic library” is very big. Template metaprogramming deservedly gets a lot of the blame, but implicit heap management via constructors/destructors is also pretty hard to follow. The upshot is that “professional grade” C++ is often impenetrable (I tried to understand the implementation of boost::intrusive_list once. Yikes.) LLVM is often cited as a very clean codebase and I think that holds up. Facebook’s folly is another good one (although it occasionally dives into template metaprogramming madness). Hopefully I’ll be forgiven for also plugging a few projects I used to work on, that might hit a sweet spot between utility and code complexity: - Glow, a compiler

It's a backend engine; it doesn't support languages out-of-the-box. That said, it's extensively used by the open-source Android bytecode optimizer [Redex](https://github.com/facebook/redex), so there's code readily available if you want to do Android bytecode analysis with SPARTA.

Signed Constant Domain: https://github.com/facebook/redex/blob/master/service/consta... Constant Array Domain: https://github.com/facebook/redex/blob/master/service/consta... Pointer domain: https://github.com/facebook/redex/blob/master/service/escape... Type domain: https://github.com/facebook/redex/blob/master/libredex/IRTyp...

You shouldn't need to change your proguard config to use redex. For mapping files, the one thing that can trip people up is that we strip out source file names. After you run redex there should be a /tmp/filename_mappings.txt to do the back-mapping, similar to proguard. If you're using third-party crash reporting tools that don't understand that back-map, though, you can always turn off the source stripping. We describe how to do that here: https://github.com/facebook/redex/blob/master/docs/Config.md.