Will the next C standard or any of the ones after that increase the libraries to support the things that C++ is like multi-threading or networking?
Will the next C standard or any of the ones after that increase the libraries to support the things that C++ is like multi-threading or networking?
Doesn't C already support this through POSIX and BSD sockets?
POSIX is not C.Originally Posted by valaris
POSIX is one standard and C is another.
I don't believe that C++ has standard support for multi-threading or networking, and I doubt that either of the new standards for C or C++ will encompass any networking functionality into the standard library. C and C++ is used for a huge number of systems on various architectures. Not all of the OS's that are used to run C or C++ on will have networking, and I don't think you will ever see more than about a few of the standards committee members agreeing on WHICH standard the networking functions would have.
Some support for multithreading is part of C++0X as far as I understand, and a new C standard may well follow those basic principles.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
How can that be? Just as not all systems support networking, not all systems support multithreading either.
Good point. I don't know why that is. But I expect that compiler support is somewhat needed for solving some multithreading issues, whilst supporting networking is simply a case of library code, and there is much less need for compiler support for that. It becomes libraries. A standardization layer on top of networking could be feasible, but my expectation at least would be that it's too far away from the core functionality of the language as such.
Likewise, I don't expect to see a standardized GUI library any time soon - because it's far too hairy a mess to sort out who is right and who is wrong in their ideas in that idea, and the compiler doesn't need to know even a little bit.
Edit: Here is the proposals for Multithreading: http://www.open-std.org/jtc1/sc22/wg...006/n2094.html
Of course, that is a proposal, it may change or get removed from the standard.
The full C++0X standards submissions are here:
http://www.open-std.org/jtc1/sc22/wg...2006/n2122.htm
And there is no mention of networking on that entire page.
--
Mats
Last edited by matsp; 08-08-2008 at 08:59 AM.
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
I suspect because it's a big issue and C++ is a modernization of C, after all. It was built to meet today's needs.
We're seeing a bigger leap towards more and more cores, but only in PCs, but also in embedded things.
So I'm guessing it's one of those "must have" things to keep C++ from falling down into history as an abandoned language.
Perhaps C will follow, as well.
As for GUI, I believe many want one, but it just takes too much time and money to put it together, which the committee doesn't have.
TR2 is a proposal that has a library to support networking. It is based off the asio boost networking library. Considering most of the TR1 is supposed to be in C++09, I would assume that the next standard will cover some if not most of TR2. It may not be soon but networking will happen sometime in the future.
>>How can that be? Just as not all systems support networking, not all systems support multithreading either.
Not all systems have a screen to support the iostream do they?
I don't think anything in <iostream> is specific to screens or keyboards... It's just some type of input stream and some type of output stream. Whether the input and output are keyboards & monitors, or files, or printers...
Yes I believe your right, but it's still not right for ALL systems. I would find an iostream for a gameboy pretty interesting.
Maybe not. Iostreams would be used by the system to read and write from the cartridge.
I would think the fstream would be used for that. The console has no permanent memory.
Last edited by lruc; 08-09-2008 at 06:28 AM.
fstreams inherit from iostreams IIRC
I was about to say the same thing, but then I changed my mind. I think <fstream> actually uses <istream> & <ostream>
http://www.cplusplus.com/reference/iostream/fstream/
They show fstream inheriting from iostream which in turn inherits from istream and ostream.
ifstream and ofstream inherit from istream and ostream individually.
