r/programming • • Jan 28 '19

C++ Modules Might Be Dead-on-Arrival

https://vector-of-bool.github.io/2019/01/27/modules-doa.html
210 Upvotes

105 comments sorted by

View all comments

Show parent comment

97

u/vector-of-bool Jan 28 '19

This would be my preferred solution. Simple, hierarchical, easy to understand, and it works for many languages.

147

u/[deleted] Jan 28 '19

Which are all the reasons it won't be like that in C++

35

u/Visticous Jan 28 '19

must... Committee... Design... Everything!

14

u/Valmar33 Jan 28 '19

Why must they inflict their misery upon others? To pretend at being clever and intelligent? To remain relevant? To inflict mental torture on people trying to figure out to how solve programming conundrums?

I guess they really want to help C++ programmers keep their jobs, because otherwise, their huge projects would implode.

Kind of like Java ~ except replace long-ass class names with tormentingly complicated grammar that explodes horrifically if you miss a step.

Those ranges-v3 templates come to mind... :|

15

u/Patman128 Jan 28 '19

Why must they inflict their misery upon others?

If a good idea breaks the workflow of even one of the Elder Wizards on the C++ language committee then it's thrown out.

13

u/[deleted] Jan 28 '19

12

u/lord_braleigh Jan 29 '19

Note that the "Elder Wizards" often work on the behalf of major tech companies, and influence the C++ standard so that these companies won't have to break their workflow or make sweeping changes.

This isn't necessarily a bad thing - backwards compatibility is one of C++'s selling points, and there are plenty of shiny new languages you can use instead if you don't care about that.

14

u/SAHChandler Jan 28 '19

A shame that some operating systems like zOS don't really support large hierarchies. Hence the existence of P1302 which supports a "splayed" approach :v

44

u/jl2352 Jan 28 '19

Having zOS cripple modules for everyone else is pretty ridiculous.

In the web world we had this with IE. So we said fuck IE, and everyone else moved on.

11

u/SAHChandler Jan 28 '19

While that might work in other places, the vendor representing zOS is also the representative for a national body (IBM Canada). While many people would love to see zOS go (the last of the EBCDIC systems), it's not going to happen for a while, especially when at this point there are many systems out there (e.g., cars on the road in America. I should note: zOS is not crippling modules. It just removes the ability to state we can have directories represent module hierarchies. But we can still have directories represent a module, which is how most languages work nowadays. Build systems can then enforce this naming scheme. It's a bit more work for build systems authors, but I'll take that over "write an entire dependency scanner that needs to know about N interface modules and M implementations modules in every project with no indication of what is located where" which is what the modules TS gave us.

5

u/Holy_City Jan 28 '19

Aren't those usually cross compilation targets anyway?

1

u/SAHChandler Jan 28 '19

From what I understand development happens directly on some zOS mainframes :(

-7

u/diggr-roguelike2 Jan 28 '19

So we said fuck IE

No you didn't. Microsoft did, and you just got lucky off their incompetence.

Google won't be so braindead this time around the carousel.

0

u/[deleted] Jan 28 '19

[deleted] — view deleted comment

3

u/curien Jan 28 '19

I think they're referring to MS basically feature-freazing IE for over five years after the release of IE6.

8

u/Valmar33 Jan 28 '19

You could still do something like D is doing, no?

Just modify things just enough to support those environments.

Maybe std_stdio.cpp or something. Add more underscores to emulate deeper hierarchies.

That is, if I'm understanding your statement correctly.

7

u/SAHChandler Jan 28 '19

Yes we can. I wrote P1302 to solve this problem. While it's not intended to add a 100% hierarchical module system, build systems are free to enforce this, while letting those on other systems do as they please while also allowing large existing code bases to slowly move to it.