Threading
-
If you can come up with some good advice and a real solution to the actual problem then put it there. Barna
My advice was valuable: pointing out unsafe solutions is a valid point to make.
Steve
-
If you can come up with some good advice and a real solution to the actual problem then put it there. Barna
It is better not to give any advice than giving bad advice. Is it too difficult for you to understand this?
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
If you can come up with some good advice and a real solution to the actual problem then put it there. Barna
Considering this is a worker thread I should do a single function for example convert some data it could use some resources. If you suspend the thread these resourse are still locked. So thats dangerous. You could change your design to use a state engine in a for(;;) loop breaking the whole functionality in small routines between each routine call you could check whether the thread should be closed. If you should stop the thread it can clear all the allocated resources and stuff. To signal if the thread should be stopped you can use synchronization objects. CEvent for instance. Even simpler can be to use the functions InterlockedIncrement which increment a long variable in a threadsafe manner.
codito ergo sum
-
Here you can find a lot a information about threads: http://www.codeproject.com/threads/usingworkerthreads.asp[^] of course,...also the way to braek it in simple way.
Cheers, Russell
sorry. actually i thought its the c# forum
My small attempt...
-
My advice was valuable: pointing out unsafe solutions is a valid point to make.
Steve
-
It is better not to give any advice than giving bad advice. Is it too difficult for you to understand this?
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
Look dude, I just pointed out that your solution was bad. This took me 5 seconds and one line of text. I post heaps of messages on this forum and make an effort to be helpful – when time permits. Now I’m sorry if you’ve been offended but nevertheless my post has merit and is informative. Perhaps not as immediately useful as a full solution: but knowing what not to do should not be underrated. Perhaps it’s taught you something for example.
Steve
-
It is always better to concentrate on the problem posted than comparing ideas.Is it too difficult for you to understand this? Barna
BarnaKol wrote:
It is always better to concentrate on the problem posted than comparing ideas
Agreed. At the same time, when someone is giving a bad advice, we can point that out. Any sane person would realise his mistake, instead of arguing after giving wrong advice on a public forum.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
Look dude, I just pointed out that your solution was bad. This took me 5 seconds and one line of text. I post heaps of messages on this forum and make an effort to be helpful – when time permits. Now I’m sorry if you’ve been offended but nevertheless my post has merit and is informative. Perhaps not as immediately useful as a full solution: but knowing what not to do should not be underrated. Perhaps it’s taught you something for example.
Steve
Steve, please stop arguing with him. Any person with a civic sense must have understood that what he did was a mistake by now. Ironically, he keeps arguing.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
Look dude, I just pointed out that your solution was bad. This took me 5 seconds and one line of text. I post heaps of messages on this forum and make an effort to be helpful – when time permits. Now I’m sorry if you’ve been offended but nevertheless my post has merit and is informative. Perhaps not as immediately useful as a full solution: but knowing what not to do should not be underrated. Perhaps it’s taught you something for example.
Steve
Look dude, What is of use to know how long it took you to understand and how many lines you wrote. What is of use to know how big heaps of messages you post in this forum.You dont have the actual solution lacks your merit. Why "Perhaps not as immediately useful as a full solution". Why not the full solution. My posts have also taught you how to post messages. Barna
-
Steve, please stop arguing with him. Any person with a civic sense must have understood that what he did was a mistake by now. Ironically, he keeps arguing.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
Look dude, What is of use to know how long it took you to understand and how many lines you wrote. What is of use to know how big heaps of messages you post in this forum.You dont have the actual solution lacks your merit. Why "Perhaps not as immediately useful as a full solution". Why not the full solution. My posts have also taught you how to post messages. Barna
I'm going to take brahmma's advice and stop arguing this issue after this post. But first I'll say this: Your advice was bad, pure and simple. In fact it was very bad as it creates a class of bug that's very hard to track down and is nondeterministic. Now again I reiterate that I’m sorry if you got offended or embarrassed, but I’ve taught both you and potentially the OP a valuable lesson. I have spent as much time on this issue as I can afford to, I’m sorry if this isn’t good enough for you. There is no law that says I can only respond to the OP: the threads are hierarchical after all.
Steve
-
It is better not to give any advice than giving bad advice. Is it too difficult for you to understand this?
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
Here you can find a lot a information about threads: http://www.codeproject.com/threads/usingworkerthreads.asp[^] of course,...also the way to braek it in simple way.
Cheers, Russell
Yeah I think all your answers and examples are going to be in that article. I hadn’t see that article before and I’m just going to read through it now and it looks pretty good. a little tip bit. 1) make sure that if you pause or stop a thread that you handle memory allocation and de-allocation. 2) try to avoid methods such as global variables to control threads and use of sleep() in a GUI based thread or thread that takes messages. Good looking article and well worth the read thanks for the link :)
-
There is no point in any argument with persons or persons who does not know how to write a line of text. Any person with a civic sense moral attitude and good characteristics must have understood that till now.
BarnaKol wrote:
There is no point in any argument with persons or persons who does not know how to write a line of text. Any person with a civic sense moral attitude and good characteristics must have understood that till now.
Then why in the hell are you replying to me, when I am not interested in talking to you any more and when I was speaking to Steve? This pretty much proves what I said. :)
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
BarnaKol wrote:
It is always better to concentrate on the problem posted than comparing ideas
Agreed. At the same time, when someone is giving a bad advice, we can point that out. Any sane person would realise his mistake, instead of arguing after giving wrong advice on a public forum.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
BarnaKol wrote:
without guggling on the ideas come with a solution to the actual problem posted.
When you are wrong, don't correct others. I will give a solution when I know it. I will not run around like you and give a solution that is erroneous.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
I'm going to take brahmma's advice and stop arguing this issue after this post. But first I'll say this: Your advice was bad, pure and simple. In fact it was very bad as it creates a class of bug that's very hard to track down and is nondeterministic. Now again I reiterate that I’m sorry if you got offended or embarrassed, but I’ve taught both you and potentially the OP a valuable lesson. I have spent as much time on this issue as I can afford to, I’m sorry if this isn’t good enough for you. There is no law that says I can only respond to the OP: the threads are hierarchical after all.
Steve
-
BarnaKol wrote:
without guggling on the ideas come with a solution to the actual problem posted.
When you are wrong, don't correct others. I will give a solution when I know it. I will not run around like you and give a solution that is erroneous.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936
-
If I dont correct you how do you know that by the time you put a solution or at least show some way out the person himself will be able to solve it. I dont run around. But it seems you are running out.
I've been with this board for quite a while. I am active on the C++ forum and I help people, whenever I can. I do not mislead them. With your message count and the content of your messages, anyone who reads this message will be able to tell that you are nothing more than a stupid little troll. I stop talking to you here. Now, we have another Kyle. You can continue with your absurd little rant.
"The difficulty lies, not in the new ideas, but in escaping from the old ones." -- John Maynard Keyes, 1936