https://en.wikipedia.org/wiki/SPARK_(programming_language)
https://www.amazon.com/Building-High-Integrity-Applications-...
Note: The book is designed for people without formal methods background. I can't say how easy or not it will be since I just got it. :)
Are we there yet? 20 Years of Industrial Theorem Proving with SPARK
https://proteancode.com/keynote.pdf
IRONSIDES DNS illustrates it can handle bigger problems
http://ironsides.martincarlisle.com
Frama-C and SPARK both build on Why3 platform with its intermediate language WhyML. Work built on any of these three can usually be ported to the others. So, I'll drop a recent example in Frama-C that's really math heavy with a style amenable to high automation.
A lot of dev's avoid dynamic allocation altogether, because of the issues you can face:
* Integer overflow
* Buffer overflow
* Free does not mean freed memory. It means freed memory at some point in the future.
If you want something safe, time-tested and performant for business logic, then something like Ada would be a better fit.
If you don't mind the safety problems, then just about nothing beats out FORTRAN in the numbers game. (Though the memory pitfalls are huge). It was one of COBOL's main competitors, and half of the world's banking infrastructure still runs on it.
Serpent and LLL are apparently lower-level than Solidity.
https://steemit.com/ethereum/@balzss/the-many-languages-of-e...
Or someone could add some analysis stages to the solidity compiler since all the information you need is floating around the web in various papers -- actually spent a good part of the last week reading about abstracting abstract machines and static analysis for my next investigative coding project when I quit being lazy.
I don't know, how about Cobol? I'm serious, that was designed as business language at least.