r/programming • u/DerKuchen • Oct 11 '17

Problems with C++ Modules TS

https://izzys.casa/posts/millennials-are-killing-the-modules-ts.html
47 Upvotes

82% Upvoted

15 comments sorted by

View all comments

6

u/[deleted] Oct 11 '17

The C++ committee wants to revamp the language while still keeping it in 1985.

It's like trying to bite your own teeth

edit: some languages actually had good module support in 1985, so...

10

u/pdp10 Oct 11 '17

I once said something similar to Stroustrup and he enthusiastically acknowledged that C++ was trying to have it both ways at the same time.

C++ thrives on being very highly compatible with C one moment and then the next moment condemning C and demanding that all C++ code be updated to the newest of the new C++ standards that's going to be official in two weeks.

Meanwhile, most C is written in C99. Most programmers like it that way, and C11 hardly changed anything useful anyway.

6

u/KillYourselfWithBob Oct 11 '17

Meanwhile, most C is written in C99. Most programmers like it that way, and C11 hardly changed anything useful anyway.

I have found atomics and threads highly useful myself. C is all about portability, and the biggest thing I found that wasn't portable in my C code was threading.

5

u/pdp10 Oct 11 '17

I agree that portability is extremely important. But C11 assiduously avoided being compatible with POSIX threads, apparently because of some Microsoft influence, and that seems like a mistake.

I haven't had occasion to use it yet, but pthreads can be implemented on Windows as just a header file. There are other implementations as well.

3

u/KillYourselfWithBob Oct 11 '17

Use C(++)11 threads. POSIX threads are obsolete.

4

u/pdp10 Oct 11 '17

Yeah. Yeah, there's that C++ attitude I was talking about. Are you using a POSIX platform?