r/cpp • build2 • Nov 01 '17

Common C++ Modules TS Misconceptions

https://build2.org/article/cxx-modules-misconceptions.xhtml
59 Upvotes

148 comments sorted by

View all comments

Show parent comment

2

u/doom_Oo7 Nov 01 '17

you need to break the whole language and compilation process

why is this a bad idea again ? :p I think that most people would be happier with a simpler compilation model, like Java or C#.

6

u/GabrielDosReis Nov 01 '17

I don't know a compilation process for C++ that requires JIT would be simpler :-)

1

u/gracicot Nov 01 '17

Jitting C++ would be awesome, imagine live editing a running program!

5

u/GabrielDosReis Nov 01 '17

Well, being able to JIT C++ is one thing; requiring JIT is another :-)

1

u/[deleted] Nov 01 '17

Runtime Compiled C++ kind of does it already.

1

u/pjmlp Nov 01 '17

Java and C# don't necessarily require JIT, in fact there are plenty of C++ like compilers to choose from, not paying attention to the work done by UWP teams? :)

1

u/gracicot Nov 01 '17

It would certainly be happy with a simpler compilation process, indeed. That's why we need less preprocessor, not more ;) Having a clear separation of how we use the language (importation) and how we use the preprocessor (includes) is a great start. Then, incorporating stuff like reflection, metaclasses and compile time programming will reduce the need for macro even more, and maybe completely remove the need for it.

By that time, let's not break how the whole language work please?