I'm a big fan of Ragel (http://www.colm.net/open-source/ragel/) but I'm biased because I coded it's Go support.
On Tue, Dec 15, 2015 at 11:01 AM, Jeffrey Goldberg <jeff...@goldmark.org> wrote: > Hello, > > I work for a company that produces a consumer product for a number of > different operating systems and environments as well as running a web > service (written in Go). Although I’ve been telling people to not use > ad-hoc parsers and adding a new regex each time someone discovers a bug, > it would be much much easier to persuade/force developers to do things > right if I can actually offer them something concrete. > > Our needs are (mostly) textual. So we don’t need things like Hammer or > Nail. I’m really old and so I think of lex/yacc (or perhaps flex/bison), > but I am hoping for things that might be better suited to simple > deterministic Context Free Grammars. And I would make our developers > happier (i.e., more willing to comply) if the parser-generators produce > code that they can link and use easily. > > So what I need is help from the langsec community in selling doing things > the right way among the developers where I work. Me talking abstractly > about “write a grammar, generate a parser from that grammar, and validate > with that parser before doing anything else” would go much better if I > could actually show people how to do that and how it will make things > easier for them. Also me saying “I told you so” with every new input > validation bug, is getting tiresome. > > So I would like to write a grammar (of, say, the subset of RFC2822 email > addresses that we want to accept) once and offer a practical way to get > from that grammar to a validator for languages and development environments > including Go, JavaScript/TypeScript, C#, Objective-C, and (perhaps) Delphi. > > Go and JavaScript/Typescript would be the big sell. I realize that for > some environments we might just have to build from C and link from that. > > So what are the parser-generators y’all actually recommend to developers > that they can easily and practically use? > > Cheers, > > Jeffrey Goldberg > > > > > _______________________________________________ > langsec-discuss mailing list > langsec-discuss@mail.langsec.org > https://mail.langsec.org/cgi-bin/mailman/listinfo/langsec-discuss >
_______________________________________________ langsec-discuss mailing list langsec-discuss@mail.langsec.org https://mail.langsec.org/cgi-bin/mailman/listinfo/langsec-discuss
