Multithreading

developing

What do you preferred for multithreading? .NET or C++?

i am doing a report on the caveats/advantages; any platforms for comparison? ideas? comments?

Plater

I honestly think threads are easier to understand in c++ then in .NET
Closing threads threads seems to be easier in c++ too. I guess I dislike how often I do my threads wrong in .NET and they stay open after my program closes

developing

interesting. invaluable personal opinion/experience...thanks

any specific links on the internet regarding c++?

Knuckless

My topics are always close when i close application(FormClosing event and Thread.Abort) if that dont help GetCurrentProcess.Exit(). Threads in .NET are easy

Plater

Easy to setup yes, but if they're doing IO and are "busy" they won't always exit.
I started insterting things into the Disposing() function of the form to deal with it better.

developing

Quote:

Originally Posted by Plater

Easy to setup yes, but if they're doing IO and are "busy" they won't always exit.
I started insterting things into the Disposing() function of the form to deal with it better.

for specifically that, you can use threadName.Join()

it will stop the calling the thread till threadName finishes execution...obviously standard warnings about threads apply

Plater

Hmm I am starting to like the form.closing sugestion.
There have been times when the delegate callback for the thread (so that it can update the gui) throws exceptions because it has fired the callback after the form has disposed of its controls.
Interesting.

Multithreading

re: Multithreading

re: Multithreading

re: Multithreading

re: Multithreading

re: Multithreading

re: Multithreading

Similar .NET Framework bytes

/bytes/development

/bytes/it

/bytes/about