User Ratings

★★★★★
★★★★
★★★
★★
3
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • One of the coolest pieces of engineering out there. Great job!
  • hi IS coflo install in windows 7?if not i am new in linux (ubuntu) .i cant install dparser with the command : tar zxvf filename.tar.gz then ./configure but it dosnt install,plz help me the error isbash: ./configure: No such file or directory many thnaks
  • Having tried pretty much all the parser generators in existence at one time or another, I can say with some authority that DParser is the one to use when you just want to get stuff parsed. No worrying about whether your grammar is LL(1)/LR(1)/LALR(1)/LL(*)/ambiguous/whatever, no fighting an artifical separation between lexer and parser, nothing: it just works. I can only ding DParser on two things: - Documentation. The documentaion is mostly adequate, especially if you've done battle with all the other options out there, but I think if the docs were a little more thorough, DParser would be the first and last stop for many of us searching for such tools. - Your program has to link with DParser's library. This library is installed at DParser-install time. This pretty much forces either your users to install DParser if they want to build your program, or you to include the DParser distro in your program's source distro. It would be a lot nicer if there was an option to have it generate all the necessary source for your parser, more like the Bisons and Yaccs of the world. Bottom line: Use DParser, get stuff parsed.
    1 user found this review helpful.
  • Previous
  • You're on page 1
  • Next