4 ms·

I remember this study about the use of final and const keywords in Java/C. http://dl.acm.org/citation.cfm?id=2884798&CFID=985095807&CFTOKEN=21584072 http://dl.

I remember this study about the use of final and const keywords in Java/C. http://dl.acm.org/citation.cfm?id=2884798&CFID=985095807&CFTOKEN=21584072 http://dl.acm.org/citation.cfm?id=2884798&CFID=985095807&CFT... It's a small example, maybe it's a start.

taeric 9y ago
Fun read, thanks for sharing! It is just a start, so I am hesitant to pick at it. I am excited to see this getting explored, I was hoping for a dive into bug reports against software, though. That is, I share the same bias most of software developers share that mutable code is ultimately dangerous and should be avoided. The flipside, only when working with established codebases does this really bother me. Greenfield projects that are not close to shipping are usually quite clean and not a concern. Battle worn codebases, though... To that end, the CWE attempt (https://cwe.mitre.org/ https://cwe.mitre.org/) was an interesting start. Especially if it was backed by numbers in the CVE database. So my question is, how many of the CVE reports could have fully been laid to this class of bugs? (I'll see if I can put together a notebook going over this idea. Still hoping someone else has already given this a better treatment than I am likely to.)