3 ms·
From your linked post: > https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pdf https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pd... It stil
by catnaroek 10y ago
From your linked post:
> https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pdf https://www.cis.upenn.edu/~eir/papers/2013/ironclad/paper.pd...
It still relies on dynamic checks. So you still have the same problem as in Java: just because you have a reference, it doesn't mean you actually have a valid object. You can make any language trivially safe by checking absolutely everything at runtime, but the whole point to using a language like C++ is to not incur in unnecessary performance overheads.
> http://research.microsoft.com/en-us/um/people/marron/selectpubs/Undangle.pdf http://research.microsoft.com/en-us/um/people/marron/selectp...
Have you actually read the paper? This isn't a static analysis at all. It just makes a dynamic analysis more eager and precise.
- nickpsecurity 10y agoAppreciate insight on first link. Far as other, that's my mistake given I only read parts on anslysis, diagnostic, and performance. It was in a list of static anslysis stuff I found. So, I wrongly assumed it was static analysis instead of verifying it myself as I did first one on that page [that worked but had limitations].