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

I would improve this as much as having groups of these special chars like [] () ; {} =. Each line that has more than 2-3 of these groups contained is a line of code.

Honza
– Honza

2011-06-28 08:19:53 +00:00
Commented Jun 28, 2011 at 8:19
...and also look for common strings in the most common languages, e.g. " = someword();" for most curly bracket languages, XML-like syntax like "<something>" and "<ab:cde>", and other common strings in other languages. I do believe some sort of lookup table of common syntax would be a good solution, as you can expand it when you find new languages to implement.

Arve Systad
– Arve Systad

2011-06-28 08:27:54 +00:00
Commented Jun 28, 2011 at 8:27
You should probably drop pseudo code. Some people like to write it as a C-style language but other people will use plain english with something that looks closer to VB6

James P.
– James P.

2011-06-28 14:25:48 +00:00
Commented Jun 28, 2011 at 14: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 »