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*
-
59@X.L.Ant: many (maybe even most) C compilers are written in C.Jörg W Mittag– Jörg W Mittag2014-12-22 11:07:01 +00:00Commented Dec 22, 2014 at 11:07
-
34@Neil: C++ doesn't compile to anything. C++ is a language. Languages don't compile, compilers do.Jörg W Mittag– Jörg W Mittag2014-12-22 11:07:44 +00:00Commented Dec 22, 2014 at 11:07
-
12@X.L.Ant: I don't think so. But the first Oberon compiler, for example, was written in Oberon and then hand-translated (which is a form of compilation, I guess) to Fortran. This compiler was then compiled with a Fortran compiler, the resulting Oberon compiler was used to compile the Oberon compiler and from that point on, the previous version of the compiler was used to compile the next one.Jörg W Mittag– Jörg W Mittag2014-12-22 11:10:48 +00:00Commented Dec 22, 2014 at 11:10
-
19@Neil It's not really that pedantic. It's accurate: a language is a spec. It may be implemented as a compiler, as an interpreter, a hybrid, etc. You can write a compiler for a language, but the compiler is not the language. I guess the issue gets confusing because there are languages for which there is no spec written anywhere except for its reference implementation. But even in those cases, I'd argue the language (i.e. the ideal the author had in his/her mind) is different from the implementation/compiler/interpreter/etc.Andres F.– Andres F.2014-12-22 12:54:33 +00:00Commented Dec 22, 2014 at 12:54
-
26Downvoters: this is a pretty reasonable question with a clear answer. That the answer is "no" is no reason to downvote. Instead, consider answering and explaining.Andres F.– Andres F.2014-12-22 12:57:15 +00:00Commented Dec 22, 2014 at 12:57
|
Show 48 more comments
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>
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. design-patterns), 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
lang-c