Timeline for What to do if the asker's code contains bugs?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2014 at 17:59 | comment | added | Marc-Andre | In this specific case doing two actions back to back is not much IMO. I understand your point though, and I would not close a question just because it has a bug like multithreading bugs, race condition and complicated behavior bugs, those are not worth of off-topicness. | |
| Jul 23, 2014 at 17:53 | comment | added | svick | Try the program as a regular user? Yes. Do everything a regular user could? I think that's asking too much. | |
| Jul 23, 2014 at 17:33 | comment | added | Marc-Andre | @svick Well the Op did not test his code properly since the bug is easily identifiable by using the application (using the AC button then doing another action). "To the best of your knowledge" I'm pretty sure he could have find it if he would have tested his code a bit more. I would consider the best of your knowledge to at least try your program as a regular user. | |
| Jul 23, 2014 at 17:25 | comment | added | svick | The rules say (emphasis mine): “To the best of my knowledge, does the code work?” So, if the OP didn't see the bug, the question shouldn't be closed. | |
| Jul 23, 2014 at 16:23 | history | edited | Vogel612 | CC BY-SA 3.0 |
corrected minor grammar errors, fixed bulleted list below hr and bolded the I for emphasis.
|
| Jul 23, 2014 at 15:47 | history | answered | Marc-Andre | CC BY-SA 3.0 |