Re: Multithreading differences in c++ and c#
* ManicQin:
Where ever you read it said that c++ Doesn't Contain Built-In Support
for Multithreading.
and the Answer for why doesn't it contain is that c++ didn't want to
give "one size fits all" solution (unlike C#).
(if you read any article about the subject you will find those exact
words)
My question is:
*what CANT I do with c# that i Can do with c++? (in Multithreading i
mean...)
Both C# and C++ are Turing-complete languages. That means that you can
do anything, as long as you're prepared to front the cost, e.g. waiting
very long for results, adding suitable i/o hardware, so on. This cost
includes the cost of using Windows (here disregarding the Mono CLR),
e.g. for the purpose of controlling a fridge or -- a ship of war.
*what do I miss with C#'s "one size fits all" solution?
Freedom to choose.
E.g., co-routines can be efficiently implemented in C++, and in Windows
you can implement the C++ interface in terms of of Windows' fiber APIs.
However, mostly the commentary I've seen, in the context of Java (but I
think it's relevant to C# also), focuses on synchronization primitives.
(I posted this question here and not in C# group because... well
because I don't think that they understand what they are missing...)
Heh.
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]