Skip to main content
8 events
when toggle format what by license comment
Jan 20, 2016 at 23:32 comment added DCShannon Mason, Frank can be abrasive and absolutist, and often refuses to admit he's wrong. He's usually right, though, and he is this time. You need to recognize you're acting the same way. Repeating your own advice: let it go.
Jan 18, 2016 at 9:27 comment added justhalf I'm curious, in your answer you kind of claimed that the save thread must be the only one modifying the game data, or else race condition might happen (if the other thread happens to be modifying the game data), and this would result in frequent save corrupt. But couldn't the message handling thread be the only other thread running together with the save thread? Then if the programmer had programmed WM_CLOSE to immediately close the window, then it will be immediately closed, and save might be corrupted (which won't happen if you don't close while saving, so no frequent corrupted save)
Jan 17, 2016 at 21:33 comment added MrLemon Your answer was not necessarily highly upvoted and accepted because it is right, but because it sounds about right. The thing about Arqade is that most users are not programmers and a lengthy answer going into technical details in an unknown field attracts upvotes just because "this guy seems to know his stuff!" (I know my own upvote came from that direction). However, Frank and MBraedley are raising valid points, and considering they both bring the exact same credentials as you do, and are adamant that your answer is wrong, there is indeed something to be corrected here.
Jan 17, 2016 at 21:17 comment added MBraedley @MasonWheeler I am, like Frank, a programmer. In fact, I'm a Windows programmer. More than that, I'm a Windows GUI programmer. I know what can happen when processing an event like WM_CLOSE. The fact is I've seen cases where the program hits an exception and drops out of the event routine half way through without any indication to the user! If you hit such an exception half way through a save (unlikely, but possible), then you've just corrupted that save.
Jan 17, 2016 at 20:13 comment added Frank If this cannot happen, you can show us proof. Any proof. It doesn't have to be of a game not being able to corrupt a save. It could be something like making a small proof of concept where you prove everything gets funnelled through the WM_CLOSE command. And has for twenty+ years. The point is, if you're going to make a statement, the onus is on you to prove it. Doesn't have to be concrete proof, but at least an effort should be made.
Jan 17, 2016 at 20:07 comment added Mason Wheeler @Frank What part of "don't ask someone to prove a negative" do you not understand? My answer is obviously correct to anyone who understands concurrency. Provide a counterexample or you're doing nothing but straight-up trolling.
Jan 17, 2016 at 20:05 comment added Frank Thank you for demonstrating exactly the same behaviour as you did on the answer. Your answer is wrong. You refuse to prove it. Therefore, we have to do something about it.
Jan 17, 2016 at 20:04 history answered Mason Wheeler CC BY-SA 3.0