Help with Visual studio

[flat jacinth]

Did I do something wrong or...

[inland path]

When your question is answered use !solved to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.

@flat jacinth

Screenshots!

Your message appears to contain screenshots but no code. Please send code and error messages in text instead of screenshots if applicable!

[deep elbow]

We need more information to help you, namely how you're compiling the code

Send your tasks.json

[flat jacinth]

Ok

[deep elbow]

Use g++.exe instead of gcc.exe

[flat jacinth]

To run the code?

[deep elbow]

Setup a launch.json file

[flat jacinth]

Yup did that

Now?

[silk gazelle]

What now?

If you replaced gcc.exe with g++.exe in your tasks.json as suggested, your problem should be fixed now

Here's a full tutorial on setting up VSC, by the way: https://github.com/HolyBlackCat/cpp-tutorials/blob/master/tooling/README.md

[flat jacinth]

How do I do that

[silk gazelle]

You have this file. Edit it to replace gcc.exe with g++.exe (in two places). Press "save"

[flat jacinth]

Ok

It gives me this yellow underline

Oh nvm I keep those the same I think

[silk gazelle]

Yeah, keep this. That's why I said to replace gcc.exe -> g++.exe, and not just gcc -> g++

(To be honest, you're better off removing this "$gcc" completely, it does more harm than good, but it doesn't matter now)

[flat jacinth]

I'll see what happens if I remove it

But ye I ran the code and it worked

Ty!

[inland path]

@flat jacinth Has your question been resolved? If so, type !solved :)

[silk gazelle]

FYI what "$gcc does is that it creates the red squiggles on errors when you press "compile", and them makes them linger until you compile again

Which is really useless, because VSC already shows red squiggles without it, and updates them in real time

[flat jacinth]

Interesting