You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- $\begingroup$ Compilers have a front end and a back end. The concepts you mention are used in front end stages, lexical analysis and parsing, often via tools like lex/flex and yacc/bison. Back ends, doing optimization and code generation, use less formal methods. Interestingly, I believe Latex, based on Tex, is a macro system and I’m not sure whether it uses a parser at all... $\endgroup$user46107– user461072020-02-22 15:22:50 +00:00Commented Feb 22, 2020 at 15:22
- $\begingroup$ @Daniel No, I suppose it wouldn't. But the result produced by this compiler is not LaTeX (nor TeX macro expansions), so the tokens produced by the lexing stage have to be parsed somehow, no? $\endgroup$sesodesa– sesodesa2020-02-22 16:07:42 +00:00Commented Feb 22, 2020 at 16:07
- 1$\begingroup$ If your thesis is focused on a specific compiler (can you share which it is?) it may use very ad-hoc or fully formal techniques - you have to dig into the code. If you can expand discussion to compilation in general, you are on safe ground, as the theory is very much applied in real implementations. $\endgroup$user46107– user461072020-02-22 16:52:09 +00:00Commented Feb 22, 2020 at 16:52
- 1$\begingroup$ @DanielMGessel, TeX uses an ad hoc hand-written parser (surprisingly, as Knuth did fundamental work in parsing, and his professors were famously miffed that as an undergraduate he did more working on compilers during break than they did in a full year). $\endgroup$vonbrand– vonbrand2020-02-23 16:37:32 +00:00Commented Feb 23, 2020 at 16:37
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. complexity-theory), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you