No C++ 'new project'

[LoganDark]

C++ support is advertised, however there are no issues/pull requests about it, there is no 'empty' project in the app itself, and there is no documentation regarding it anywhere.

What's going on? Is C++ actually supported, or are you just assuming it's the same as C?

[yurydelendik]

What's going on? Is C++ actually supported, or are you just assuming it's the same as C?

C++ and C are using the same clang service. Minor changes will be required in the build.ts code of C 'empty' project. Having an 'empty' project for C++ may be useful.

[LoganDark]

What changes would be required? Sorry, I'm not well-versed in this sort of thing.

[yurydelendik]

file names

[LoganDark]

That's it?

[yurydelendik]

[LoganDark]

Ty!

[rabbitHX]

@yurydelendik Hi, only single c(c++) file compile is workable now, how to compile project with header files? I read source code of clang-heroku-slug and WebAssemblyStudio but didn't find support for header file.

[yurydelendik]

The "headers" work is done at #365

[LoganDark]

#include is literally copy-paste why do you need a separate fix for it wtf

[yurydelendik]

#include is literally copy-paste why do you need a separate fix for it wtf

copy-paste of what? what's a separate fix?

[LoganDark]

#include "filename" is (and always has been) replaced by the preprocessor with the contents of filename

The separate fix that I don't know why you need is #365, which supposedly makes #includes work.

The reason why I don't know why you need it is that, if one file works, #includes should too, since it just compiles (or puts) all the code into one file (not to be confused by the actual compilation step) like copy-paste...

edit: Wait, is that fix just 'supporting' .hpp files in the editor? How was that not already supported? I'm really confused now...

[yurydelendik]

#include "filename" is (and always has been) replaced by the preprocessor with the contents of filename

Not that simple: #include works in combination with #ifdef to stop recursions. Also, the proposed copy'n'paste hack does not provide debug information: original file line numbers.

@LoganDark In the future we also need to support "inclusion" of custom libraries (headers files + wasm objects/libs), so #365 will be needed.