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.

Required fields*

Rev

Thanks for your answer (also for the brief excursion to C#). Easy reviewing is of course an important point, especially in Open Source projects. With cheap returns in modern C++, these considerations will lose their importance. With older legacy software and it's aged compilers it may be still helpful.

Wolf
– Wolf

2015-10-05 14:18:22 +00:00
Commented Oct 5, 2015 at 14:18
I didn't forget about it, but C++ Core Guidelines is not as quick to get. It's interesting that it's Philosophy shows the rationale behind the rules and also a modernized view on programming ("Express ideas directly in code" reads a little bit like the Zen of python) as a way to communicate.

Wolf
– Wolf

2015-10-05 14:37:27 +00:00
Commented Oct 5, 2015 at 14:37
Supplement: direct link to the Philosophy section of the C++ Code Guidelines.

Wolf
– Wolf

2020-02-19 08:30:37 +00:00
Commented Feb 19, 2020 at 8:30

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 »