Re:Writing parsers like it is 2017
by staticassertion on Tuesday August 15, 2017 @11:28AM
(#15019121)
This is always going to lead to the same place - whether it's the developer's fault or the tool's.
The author of this post wants uncompromising safety, ragel does not allow for that - programmer error can introduce memory unsafety. They even explicitly call out Cloudbleed.
The author of this post wants uncompromising safety, ragel does not allow for that - programmer error can introduce memory unsafety. They even explicitly call out Cloudbleed.