tag:blogger.com,1999:blog-4222267598459829544.post8216647820029771160..comments2024-03-15T00:28:25.403-07:00Comments on Ben Lynn's Online Garbage: Reentrant parsers with Flex and BisonBen Lynnhttp://www.blogger.com/profile/09117417699962852340noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4222267598459829544.post-3421067335732411572013-12-20T10:09:12.747-08:002013-12-20T10:09:12.747-08:00My experiences have been similar, e.g. I wrote a g...My experiences have been similar, e.g. I wrote a goyacc-compatible lexer for Go (http://cs.stanford.edu/~blynn/nex). But I still use C when I want speed.Ben Lynnhttps://www.blogger.com/profile/09117417699962852340noreply@blogger.comtag:blogger.com,1999:blog-4222267598459829544.post-19284215313964467412013-12-20T09:24:33.396-08:002013-12-20T09:24:33.396-08:00Blast from the past! I haven't used Flex or Bi...Blast from the past! I haven't used Flex or Bison since almost 20 years ago when I used them for in-house tools and products involving parsing. I remember being happy about the Flex "reentrant" option, and then also getting into C++ and using C++ for both Flex and Bison to create nicely encapsulated parsers. I should still have all that code around somewhere backed up. In 1995 I did switch away from C/C++ when possible though, and ended up creating my in-house parsing apps in ML (mlyacc, mllex) and then Haskell (Happy) instead... And now I'm still parsing, but using Scala. It never ends.Franklin Chenhttps://www.blogger.com/profile/14762341306710286314noreply@blogger.com