3 ms·
I am pretty happy with the parser from MS: https://github.com/microsoft/ts-parsec#readme https://github.com/microsoft/ts-parsec#readme the API is pretty intuiti
by sAbakumoff 6y ago
I am pretty happy with the parser from MS:
https://github.com/microsoft/ts-parsec#readme https://github.com/microsoft/ts-parsec#readme
the API is pretty intuitive and it the package is reliable
Can't imagine why I would want to switch to PASUKON(what an odd name by the way).
- moogly 6y agoI believe the name is a play on a) romanization of the Japanese pronunciation of PC ("personal computer" -> "PersCom" Japanese abbreviations of English tend to concatenate the initial syllable of every word, and "n" and "m" end up sounding very similar). b) "parser combinator" would have the same abbreviation in Japanese
- gosukiwi 6y agoExactly that :) Glad someone got it! Heh.
- gosukiwi 6y agoFor me it was mostly a fun project I've always wanted to make :) I didn't know about ts-parsec though, looks cool! I originally designed Pasukon as an alternative to PEGjs. A way to quickly prototype a language and generate an usable parser. What I didn't like much about PEGjs is the lack of extensibility, so I added the ability to use your own lexer and combinators to really fine-tune the parser if needed. Also PEGjs struggles with indent-based grammars, because it can't use caching with those, and it can get quite slow. That gets solved by using a lexing step which outputs proper `INDENT` and `DEDENT` tokens.