Edit - Software Engineering Stack Exchange

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.

"But they all don't behave the same"... If the language's parser checks for syntax errors, parser errors, and properly warned for potential undefined behavior before code generation, then inspecting the outputted C wouldn't be necessary...

Kied Llaentenn
– Kied Llaentenn

2020-02-06 01:07:21 +00:00
Commented Feb 6, 2020 at 1:07
1

@KiedLlaentenn - I was perhaps unclear then? The same exact C code does not behave the same on every architecture in existence. Reasonable C code, like adding ints together.

Telastyn
– Telastyn

2020-02-06 02:01:36 +00:00
Commented Feb 6, 2020 at 2:01
ah. I misunderstood.

Kied Llaentenn
– Kied Llaentenn

2020-02-06 02:18:30 +00:00
Commented Feb 6, 2020 at 2:18

Add a comment |

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

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>

formatting help »
answering help »