All the times you can

If you have additional includes make a practice to keep them in some common directoey

And define them as additional include directory during build

What if you include file conflicts with another include file?

It should not. Use folders so something like <includes\specialtask. H>

Some people even prefix all the header files with letters based on context

Best practice is always include local project dir

For some commonnunctionalities move them to a commonnlocation

Any one pls explain g

One of the g example correct behavior could be to make demons rush out of your nose

Gotta love UB

Hello guys can anyone tell me where can i learn file handling in c++

Gotta love UB

Gotta love dragons and nasal demons

Anything can happen according to the C standard.

I'd make a compiler that would delete all your files when UB occurs.

That'd teach 'em!

I'd make a compiler that would delete all your files when UB occurs.

I'd write one that throw a SIGILL and on that signal print a dragon in the standard output

That would aslo be fun and less malicious.

I could make it use SDL_audio to play some imagine dragons in the background

Hello guys can anyone tell me where can i learn file handling in c++

I think you could find following link useful: https://www.learncpp.com/cpp-tutorial/186-basic-file-io/

Implementation defined behaviour: "here come dragons"

If that is what you need.

There be dragons.

I think you could find following link useful: https://www.learncpp.com/cpp-tutorial/186-basic-file-io/

Thanks mate

np.

How can i have a sub project dependecy using Cmake

http://thats-a.link/4EdNgsF.png

I would like to be able to include stuff from Engine in the game project

http://thats-a.link/71Uv9KH.png

So it seems to be that ../ isn't working

6.5.2.2.10 of ISO/IEC 9899:2011: There is a sequence point after the evaluations of the function designator and the actual arguments but before the actual call. Every evaluation in the calling function (including other function calls) that is not otherwise specifically sequenced before or after the execution of the body of the called function is indeterminately sequenced with respect to the execution of the called function. 94)

i.e. the order in which arguments are evaluated is undetermined.

In your case it seems like the arguments were evaluated last-to-first.

What is the best way to learn C for a beginner?

21st

What is the best way to learn C for a beginner?

21st

21st

What is the best way to learn C for a beginner?

Study the language 🤷‍♂ start reading the basics about programming and the C language and begin to write some stupid program in the meantime

There's no Learn C in 7 days available

There are some good books.

Am I right to assume you know German?

http://thats-a.link/9JSnWHA.png

Window* w = new Window();

Hello, guyz.. 😄

Hello, guyz.. 😄

Goodbye buddy 👋

Goodbye buddy 👋

Ok.. Then you go 😄

Window* w = new Window();

No

Window W()

that isn't the issue

😄👈

Window its constructor somehow is undefined

Issue is the linker

Window* w = new Window();

No auto w = std::make_unique<Window>()

If window is coming form a librari

Add it to linker

No auto w = std::make_unique<Window>()

Even better :)

http://thats-a.link/9JSnWHA.png

Well Where is the Window.cpp file in the project file structure?

Hello, guyz.. 😄

Nohello.com

@unterumarmung Yes there is

Its in the Engine/src folder

Same loc as the Window.h folder

Oh sorry

Don't use the angle <> brackets for your own headers please

Use double quotes

And why do you CMake instead of MSBuild?

CMAKE for project manage crap

like libs

And so i can more easy build on linux

cmake is great

makes building easy

Also not using <> is not a hardcore advice

Many companies strictly use <>

Anybody learning openCV?

Lol!

Stupid noobs

I sm a noob too here

🤔

Anybody learning openCV?

No meta questions are allowed. And it is actually offtopic

I;m not sure, whether it's off or ON. I asked people who are learning openCV w.r.t C++. I should've more specific lol

Use double quotes instead of angle brackets