3 ms·

If they take the C out of C++ Call it ++ Basically get rid of everything that the legacy of C brings. If you want those things you probably should be coding

If they take the C out of C++ Call it ++ Basically get rid of everything that the legacy of C brings. If you want those things you probably should be coding C. Get rid of the headers .h etc. Build that from the source .pp files Make a standard package library that works properly on all platforms. Standardize the internal symbols. Make templates / everything easier to use, make standard internal map and vector types. Change auto to var. Kinda like the way go did it. Sorry, too late!

einpoklum 7y ago
> Basically get rid of everything that the legacy of C brings. This is actually happening, but not literally. That is, most of the things you used to write in a C-like fashion - you no longer write today: * References or plain values instead of pointers. * std::arrays or other containers instead of plain arrays. * std::variant's instead of unions * std::expected instead of returning error codes (although error handling is a really complex issue) and so on. > Get rid of the headers .h etc. This will start to happen in C++20, with modules. > Make a standard package library that works properly on all platforms. The standard library works well on many platforms. If you mean package management systems - that's never part of the language; but you can check out https://conan.io/ https://conan.io/ > Standardize the internal symbols. Sort-of happening with modules, if I understand what you mean. > Make templates / everything easier to use, C++ features are actually easier to use as the standardization progresses. > make standard internal map and vector types. Whaaat?! Ha ha ha, certainly not. You really don't want that. > Change auto to var. That is rather inconsequential... > Kinda like the way go did it. What you suggested is in no way specific to Go.
72deluxe 7y ago
Templates are easy to use? The messages that come about from getting them wrong aren't always the best though. I don't understand why people want to get rid of headers at all? Can anyone explain why? In C# I have no headers and I find it far more difficult to read a class or get an overview. "make standard internal map and vector types" What do you mean by this? I want to be able to use the right container for the job. I don't want a dumb array of any type like PHP arrays. That's appallingly bad because you can above garbage into them and the user of the array has no guarantees about what is in it. Might as well use void* everywhere and chuck the type system in the bin if you really want that? Or have I misunderstood? Also changing auto to var - why??

einpoklum 7y ago

> Basically get rid of everything that the legacy of C brings. This is actually happening, but not literally. That is, most of the things you used to write in a C-like fashion - you no longer write today: * References or plain values instead of pointers. * std::arrays or other containers instead of plain arrays. * std::variant's instead of unions * std::expected instead of returning error codes (although error handling is a really complex issue) and so on. > Get rid of the headers .h etc. This will start to happen in C++20, with modules. > Make a standard package library that works properly on all platforms. The standard library works well on many platforms. If you mean package management systems - that's never part of the language; but you can check out https://conan.io/ https://conan.io/ > Standardize the internal symbols. Sort-of happening with modules, if I understand what you mean. > Make templates / everything easier to use, C++ features are actually easier to use as the standardization progresses. > make standard internal map and vector types. Whaaat?! Ha ha ha, certainly not. You really don't want that. > Change auto to var. That is rather inconsequential... > Kinda like the way go did it. What you suggested is in no way specific to Go.

72deluxe 7y ago

Templates are easy to use? The messages that come about from getting them wrong aren't always the best though. I don't understand why people want to get rid of headers at all? Can anyone explain why? In C# I have no headers and I find it far more difficult to read a class or get an overview. "make standard internal map and vector types" What do you mean by this? I want to be able to use the right container for the job. I don't want a dumb array of any type like PHP arrays. That's appallingly bad because you can above garbage into them and the user of the array has no guarantees about what is in it. Might as well use void* everywhere and chuck the type system in the bin if you really want that? Or have I misunderstood? Also changing auto to var - why??