Edit - Stack Overflow

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.

This is good but be careful with the logic here when you implement it, OP. If you change the operator sign, you could run into problems because of the stacked elif structure. For instance, you can't flip the signs to > or you'll have problems.

jwarner112
– jwarner112

2013-11-18 20:14:54 +00:00
Commented Nov 18, 2013 at 20:14
1

After writing it, it also looked pretty difficult to maintain. I'd use a hash to store probabilities which would be much easier to maintain. Or something clean like the answer in this question, since you could easily add or remove cases.

MxLDevs
– MxLDevs

2013-11-18 20:17:45 +00:00
Commented Nov 18, 2013 at 20:17
@Keikoku Modified it a little bit and it worked great, and thanks to all the others that gave an answer all of them helped when I was modifying it to fit my needs.

user2925490
– user2925490

2013-11-18 21:35:39 +00:00
Commented Nov 18, 2013 at 21:35

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 »

Collectives™ on Stack Overflow