myThread.ThreadState == ThreadState.Stopped
-
is not equivalent to: myThread.ThreadState != ThreadState.Running Sigh. Because threads have other states, like suspended. Which it was entering waiting for an async read to finish. That was hosing up my graceful thread exit wait. Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
is not equivalent to: myThread.ThreadState != ThreadState.Running Sigh. Because threads have other states, like suspended. Which it was entering waiting for an async read to finish. That was hosing up my graceful thread exit wait. Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithYou're supposed to tease us with the question and not answer it immediately. Otherwise its less fun :D
Todd Smith
-
You're supposed to tease us with the question and not answer it immediately. Otherwise its less fun :D
Todd Smith
Todd Smith wrote:
You're supposed to tease us with the question and not answer it immediately.
In the previous post, a couple people complained about that, so I decided not to. :) Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
Todd Smith wrote:
You're supposed to tease us with the question and not answer it immediately.
In the previous post, a couple people complained about that, so I decided not to. :) Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithYeah, but getting the answer before the problem wasn't very satisfying either.
-
Yeah, but getting the answer before the problem wasn't very satisfying either.
PIEBALDconsult wrote:
Yeah, but getting the answer before the problem wasn't very satisfying either.
Ok, next time I'll do what someone else suggested. Post the problem, then a reply with the answer. That way, you're only tempted to cheat. :) Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
is not equivalent to: myThread.ThreadState != ThreadState.Running Sigh. Because threads have other states, like suspended. Which it was entering waiting for an async read to finish. That was hosing up my graceful thread exit wait. Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithMarc Clifton wrote:
Sigh. Because threads have other states, like suspended. Which it was entering waiting for an async read to finish.
Why aren't you using myThread.Join()? Better yet, most async operations return a sync object...
-
You're supposed to tease us with the question and not answer it immediately. Otherwise its less fun :D
Todd Smith
I agree, this forum looks like it is going to be a lot of fun provided everyone states the problem (entertainment) and then provides the solution.
I’ve taken the word 'impossible' out of my vocabulary, because it does not apply to software bugs.