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

1

everyone seems to agree that having a standard is the way to go.

qodeninja
– qodeninja

2011-12-19 05:00:15 +00:00
Commented Dec 19, 2011 at 5:00
Yeah, if your editor is good enough to code it will have all the configurable settings you need.

Carra
– Carra

2011-12-19 08:00:06 +00:00
Commented Dec 19, 2011 at 8:00
After you decide about style, you can in most editors (I have seen that in eclipse) export the settings to a file so that whenever someone new is joining the team, he can import from there. You might want to utilise some tools such as FXCop (VStudio) or PHP code sniffer, before commiting...

Dimitrios Mistriotis
– Dimitrios Mistriotis

2011-12-19 11:16:39 +00:00
Commented Dec 19, 2011 at 11:16
The link to the C style guide is broken

Ferrybig
– Ferrybig

2017-06-23 20:25:50 +00:00
Commented Jun 23, 2017 at 20:25

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 »