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.

Great thank you, I am trying use C practices with a grain of salt as I learn, knowing that many things may not apply high level languages.

Mwspencer
– Mwspencer

2019-03-07 19:45:43 +00:00
Commented Mar 7, 2019 at 19:45
1

This may not matter in this case but when you have gobs of stuff happening in one line, it can also be problematic for debugging. The line numbers in stacktraces can point you right at the problem when there's only one statement.

JimmyJames
– JimmyJames

2019-03-07 20:46:34 +00:00
Commented Mar 7, 2019 at 20:46

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 »