We're in fucking 2020, and a C++ program still can't be compiled if there's a space or a non latin symbol in the path.
Seems like clients are not the only one living in the stone age.

@RocketSurgeon Oh I do, but looks like IDEs do not.

What IDE? Code::Blocks works fine, so does VSCode and Visual Studio.

Poor boy, stop harassing him.
I feel you bro, everything should be Unicode nowadays.

@Lor-inc I'm using CLion

🦴

@c3r38r170 Would be cool for those having a non-latin alphabet yeah
That is not my case. gcc spit me an error in the face because it couldn't deal with the freaking brackets in the path.
Freaking. Brackets. Not like I was using fancy unicode symbols.

So compilers should be fed any old shit? Is this how you code? ;-)

No probs with GCC and spaces in path names, just quote the whole filename. However, make usually fucks up.

@Fast-Nop I thought it was gcc's fault since I didn't have any problem compiling with the path containing brackets using VS 2017 build tools but got the issue with that.
Now you're mentioning make, what fucked up initially is not that gcc failed to compile my code but failed to be tested by my IDE.

The space issue was separate, it was my IDE's fault, because it didn't wrap the path in quotes when launching compilation.

Still, gcc is not forgiven. Now my code won't compile because it doesn't support filesystem with C++ 17 (in2020dammit). But that's another problem.

Think about the implications of something as deceptively simple as parsing a file..