3 ms·
I see it mainly ending up in parsers, transforms, protocols, and function composition. That by itself would be fine given all the problems in those. Then, other
by nickpsecurity 11y ago
I see it mainly ending up in parsers, transforms, protocols, and function composition. That by itself would be fine given all the problems in those. Then, other stuff handles all the wild code that most certainly won't be LANGSEC compatible but will run the world's software. ;)
It's another tool in the toolbox. My hope is they'll find new wisdom on just how expressive one needs to be for optimal productivity, readability, and verification tradeoff. Meanwhile, there's work in DSL-based, verified kernels and software that's already gotten closer to that. A race between all of them to figure out similar things. I wonder who will win.
Example of project using DSL's for high-assurance security/correctness
http://www.cs.yale.edu/publications/techreports/tr1436.pdf http://www.cs.yale.edu/publications/techreports/tr1436.pdf