Please don't show me any error.

why

I know that it will show error

yes exactly

But, the thing is why twice?

g++ main.cpp foop.cpp foop.h

This is the build command

I'm compiling using g++ main.cpp

with #include "foop.cpp" in main

so it goes MAIN: include foop.cpp into the source compile to obj FOOP: compile to obj LINK: error i have foo in main and in foop

Is that going to give error?

I just replaced #include "foop.cpp" with the foo() definition. That's it

u must replace #include "foo.cpp" with "foo.h" if u want it works

so it goes MAIN: include foop.cpp into the source compile to obj FOOP: compile to obj LINK: error i have foo in main and in foop

FOOP

Is that going to give error?

no

[kurimi@KlimiStation tg]$ g++ main.cpp [kurimi@KlimiStation tg]$ ./a.out 42 43

That's what I was asking

So

this

I mean to say is that: #include <iostream> #include "foop.cpp" int main(int argc, char *argv[]) { int x=42; std::cout << x <<std::endl; std::cout << foo(x) << std::endl; return 0; }

won't give error on

g++ main.cpp

Right?

[kurimi@KlimiStation tg]$ g++ main.cpp [kurimi@KlimiStation tg]$ ./a.out 42 43

^ yes it wont

but dont do that

g++ main.cpp foop.cpp foop.h

What do you say to this?

Compiling many files?

or something else?

its what devcpp does

I mean what is the correct way to describe what you wrote

dont include cpp but include headers?

What is the correct way to describe this: g++ main.cpp foop.cpp foop.h

dont include cpp but include headers?

ye, it's the rule

dont include cpp but include headers?

I got you

dont include cpp but include headers?

But, that's only when you are compiling just main.cpp

What is the correct way to describe this: g++ main.cpp foop.cpp foop.h

Why isn't anyone responding on this?

What do we say to that?

compiling many files? or something else?

But, that's only when you are compiling just main.cpp

no

just include headers, the compiler will take care of the rest

from cpp code it creates .o (obj files) and then it build the program with linker

just include headers, the compiler will take care of the rest

But, it worked when we do g++ main.cpp in the above case.

yes

because you told do do only one o

just one obj file, nothing to link (almost)

So, it compiled only main.cpp

?

and what happened to foop.cpp ?

We didn't compile foop.cpp

I mean I didn't compile foop.cpp

for main.cpp to run perfectly

and what happened to foop.cpp ?

was omited

for main.cpp to run perfectly

yes

because you included it

and in what case would we need to do

g++ main.cpp foop.cpp foop.h

?

❓

g++ main.cpp foop.cpp foop.h

never include cpp file into another cpp file that is the rule

Any church management system?????

never include cpp file into another cpp file that is the rule

Well I understand that. and I won't do it.

Good

But, I'm asking is

and in what case would we need to do

g++ main.cpp foop.cpp foop.h

Any church management system?????

/report what the Hell

When?

Any church management system?????

whatcha need

Why did Klimi write this g++ main.cpp foop.cpp foop.h

Why did Klimi write this g++ main.cpp foop.cpp foop.h

because it wouldnt work

i g

oh gosh

I mean what does that do?

[kurimi@KlimiStation tg]$ g++ main.cpp foop.cpp

I've never written g++ main.cpp foop.cpp foop.h

yes you are right i dont need .h

gtg

yes you are right i dont need .h

So, when we would write g++ main.cpp foop.cpp

I've never written 2 cpp files in a single g++ command.

That's why I'm asking

whatcha need

Do u have it