analyzer

XTA Timing analyzer - can determine(i think statically) the worse case timing between any 2 points in code.

Probably worse since they're so much harder to track down than using the static analyzer or running the 'leaks' tool.

This is of course mitigated a bit by the new pluggable analyzer feature, but it does feel like a hack.

If you work at a company that can afford Coverity (static analyzer), it is great.

ClojureScript is no different, the macros files is longer than the analyzer or the compiler.

You have a parser (analyzer) that turns text into an AST, then a compiler that turns the AST into the target code.

I work at a company developing a static code analyzer to detect bugs in C/C++ software.

So I ran the Stanford (Named Entity) Analyzer on the copy of the comments so far.

Clang itself is ~400k once you exclude things like the static analyzer and all the various tooling built on top of it that's shipped with clang.

So we simply conditionalized a few key things in the analyzer and then we just point ClojureScript JVM back at its own sources.

But before you could've used the static analyzer (/analyze).

Replete doesn't yet support using external libraries, but since the analyzer/compiler is available, I don't see any conceptual barrier preventing bootstrapped environments from consuming libraries.

According to the analyzer, "Kill the unbelievers and wear their skins as crowns." is mostly open and agreeable.

You know, "record" the same sample using both cables with a logic analyzer and compare them?

I still think that what you could get would be "close enough" with a few code guidelines (or a purpose-built static analyzer).

YourKit, Coverity Dynamic Analyzer) to understand the behavior of your JRuby applications, and even attach directly to running production apps to debug them.