Live data from Hacker News

Viewing profile — bd82

bd82

HN member
Joined
Mon, Mar 07, 2016, 11:41 AM UTC
HN karma
183
Public activity
54 items

About bd82

No profile information was provided.

Recent public activity

  1. comment
    Comment #22494567

    Even the Antlr FAQ mentions that "almost no one uses parser generators to build commercial compilers." * https://github.com/antlr/antlr4/blob/master/doc/faq/general.... * See: "Wha…

  2. comment
    Comment #21774739

    Some of the top of my Head: - Antlr (https://github.com/antlr/antlr4/blob/master/doc/javascript-target.md) - PegJS (https://github.com/pegjs/pegjs) - Nearley (https://github.com/ka…

  3. comment
    Comment #21773513

    Luckily there are many Parsing Libraries in the JavaScript eco-system, So we won't have to find out if this convoluted approach is worthwhile :) - https://tomassetti.me/parsing-in-…

  4. comment
    Comment #21773472

    I develop a parsing library for fun and I don't think that would be an easy or useful interview question. Maybe it makes sense if you assume the input has already been tokenized so…

  5. comment
    Comment #21773246

    You can find it At: https://github.com/SAP/chevrotain

  6. comment
    Comment #19336373

    I've created a Parsing Toolkit (for JavaScript) which I believe fulfills 7/10 of the requirements described. Chevrotain - https://github.com/SAP/chevrotain The list of features can…

  7. comment
    Comment #19221489

    I kept putting of switching from Travis to Circle-CI in one of my open source projects, But when I did get around to it the whole thing went pretty smoothly and easily and I regret…

  8. comment
    Comment #18402405

    Thanks. Chevrotain is an LL(K) Parser library, or more precisely SLL(K), It looks up-to K fixed token ahead to choose the next alternative. Because it is just a library to assist i…

  9. comment
    Comment #18400828

    If you are looking for an alternative to standard parser generators you may wish to have a peek at Chevrotain. * https://github.com/SAP/chevrotain Instead of using an abstraction o…

  10. comment
    Comment #18400768

    Ohm has several impressive features, such as separation of grammar and semantics and incremental parsing capabilities. The base performance however very low, as in two orders of ma…

  11. comment
    Comment #17554480

    Have a look at this: https://tomassetti.me/parsing-in-javascript/#chevrotain This is Not exactly a parser generator but an internal JavaScript DSL for writing parsers, but it does …

  12. comment
    Comment #17027957

    Maybe this example will help? https://github.com/SAP/chevrotain/blob/master/examples/gramm... It is implemented using a parsing library so the lookaheads are automatically performe…

  13. story
  14. story
  15. story
  16. story
  17. comment
    Comment #16042434

    Perhaps Antlr?

  18. comment
    Comment #15493770

    Incremental parsing is indeed amazing for IDE scenarios. But you still have to parse the entire file at least once. For example it takes 15 seconds to parse lodash.js with Ohm (on …

  19. comment
    Comment #15493635

    I don't understand the question. I am not familiar with Haskell but from what I understand Pandoc is a group of hand crafted parsers (readers) for markup formats. How does this rel…

  20. comment
    Comment #15493351

    Even the creator of Antlr (Terence Parr) Said: "In my experience, almost no one uses parser generators to build commercial compilers." https://github.com/antlr/antlr4/blob/master/d…

  21. comment
  22. comment
    Comment #15492758

    It did not exactly went away. It is still possible to embed semantics inside an Antlr4 grammar. For example see the Antlr4 EcmaScript grammar sample: https://github.com/antlr/gramm…

  23. comment
    Comment #15492648

    One option would be to use a Parser that supports fault tolerance and error recovery. In hand crafted parsers this error recovery may be added manually (but resulting in a-lot of w…

  24. comment
    Comment #15492546

    Ohm is very impressive. Specifically: 1. The separation of Grammar and Semantics. 2. Handling left recursion in a top down (peg) parser. 3. Incremental parsing. I think that the on…

  25. comment
    Comment #15492449

    That is a very good question because afaik many(most?) commercial (meaning "serious"...) programing languages are developed using hand crafted recursive decent parsers which usuall…