Is there a formal (ideally BNF) typescript js language grammar (or only typescript subset)? [closed] - bnf

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
The community reviewed whether to reopen this question 2 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I'm looking for the Typescript grammar.
Not the parser-lexer, but only the formal grammar description.
I want to implement ts it's code folding and basic static code analyzing as plugin to one simple linux IDE for GNOME.

The formal grammar is in Appendix A of the TypeScript Language Reference, version 1.8 if which is found here or here (for current version)

Since typescript is a strict superset of Ecmascript 5 (http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf/), you could exend any ecmascript bnf with syntax definitions from the Typescript spec.
A starting point could be: http://www.antlr3.org/grammar/1153976512034/ecmascriptA3.g

An ANTLR4 grammar, but admittedly "not exactly ... to TypeScript standard" (it's a pain there are so few official grammars for existing programming languages):
https://github.com/antlr/grammars-v4/tree/master/typescript

Maybe you can find references in the source code, e.g. compiler/tokens.js

Related

Any thing about How to Design Components mentioned in How to Design Programs? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I've just started reading How to Design Programs (2nd edition) on htdp.org
There are several notes in this book mentioned next volume called How to Design Components (e.g. the 3rd note in part one), however, I just can't google anything about the 2nd volume book.
I'm wondering why it is so hard to find any information about the latter volume. Has it finished? If it has not finished yet, how can I get information about the book?
The first author provides more information on his website:
We have decided to provide the draft of "How to Design Classes" (pdf)
on an "as is" basis for now. You are free to download and print it.

Writing manpages in 20XX [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I wrote a program, and I'd like to write a manpage for it.
I started to learn Groff, and I really find it awful. The man macros are difficult to understand, difficult to use, and a real obstacle to productivity. The mdoc macros add a nice "semantic" extension, but they still suffer of limitations which make it incredibly hard. The resulting "code" is poor in maintainability.
Of course I know I can convert any modern markup language (say Markdown) into manpages via pandoc, but I dislike the result, and I'm not that fond of adding pandoc as dependency of my project, anyway.
Is there a way to obtain a decent manpage from a reasonable markup language?
I write manpages for the bash and ruby scripts I write.
I format them in markdown, which is a popular and simple text format.
Then I use a ruby gem called ronn to process the markdown into groff format with man macros. Ronn can also output html from the same markdown source.
OP here. After checking some alternatives, I decided to go for Asciidoc.
There are many alternatives indeed. For example, check this other question.
I also realized that there's no good answer to this question, given the fact that many tools can be used, and in the end it is just a matter of taste :)
I'll just vote for closing my own question (if anything it will remain as reference).

Parsing and generating text in Common LISP [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I would like to find a library for parsing and generating text in common lisp. I would like it to be maintained and documented and preferably with a community that could answer questions.
In the past I have used for the same job ANTLR/StringTemplate in Java and Boost.Spirit in C++. Both projects are well documented in my opinion. From what I am reading, Parsec for Haskell would also meet my requirements. But I have not found something similar for LISP. Perhaps lispers parse texts using their own hand-made parsers?
I am aware of this question, but the so-called documentation on smug is a technical report on monadic parsing, with examples in Haskell. The documentation of LispBuilder looks rather short also. Most projects in CLiki seem abandoned.
Which library would you recommend? The grammar I need to parse is not very complicated.
You might have a look at
Cl-yacc
Esrap

What are some good resources for GNU Make? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have read about 1/3 of the GNU Make manual, do you guys know of any resources to really learn the Art of using Make.
Ideally, there might be some examples where two ways of doing something are possible, and the author explains which method he chose and why.
I am primarily using Make not to build C/C++ programs but to operate a processing pipeline for data analysis.
Managing Projects with GNU Make, by Robert Mecklenburg, is the best I've come across. Plus, it's an O'Reilly Open Book, so O'Reilly gives away free PDFs of it on their website. Read it linearly, and start from the beginning (even if you think you already know the basics of GNU Make).
John Graham-Cumming has written a book called GNU Make Unleashed which looks promising, although I have not read it yet. http://www.lulu.com/product/paperback/gnu-make-unleashed/2937580 and http://jgc.org/

Pronouncing dictionaries [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
Are there any alternatives to The CMU Pronouncing Dictionary, commercial or open source?
I don't believe the answer is definitively "no," but I do know that CMU is the most popular pronouncing dictionary in my anecdotal experience. I believe it is open source so if it's missing something, perhaps you could find a way to add it (or request it be added).
Barring that, I would check with the folks at Language Log. They deal a lot with phonetics.
I am searching for something similar, too. Next to it I found http://www.voxforge.org/home/downloads
There is CELEX 2, available from the Linguistic Data Consortium, which contains phonology information and costs $300. The problem is that it's a little dated, and the English dictionary is BE, not AE.
You can use CALLHOME, too, but with $2250 it's more more expensive than CELEX.
forvo.com. Free and open.
I found DictionaryForMIDs and desktionary. I haven't used either but both are open source.
Checkout Merriam-Webster for things like this:
stack
overflow

Resources