include files that are'nt in compiler's directory

How can i include files that are not in compiler's directory.
If i write

Code:

#include<iostream.h>
or#include<folder\\innerfolder\\file.cpp>
Then this file refers to the path
 c:\\tc\\folder\\innerfolder\\file.cpp

Code:

How to include a c:\\anyfolder\\anyfile.cpp???

#include"c:\anyfolder\anyfile.h"
or
#include<c:\anyfolder\anyfile.h>

use quotes when you're including your own headers... and use relative paths...

Oh, and since it wasn't mentioned... I couldn't help but notice you had:

Code:

#include <suchandsuch.cpp>

You don't include CPP files, you only include libraries. Source code is compiled into object files which is then linked to create the executable. Libraries are combined with your source code by the preprocessor before compilation.

Not that your compiler won't accept it, it's just standard practice.

Local header files you include with
#include "header.h"

Your own library headers, or library headers for 3rd party libraries you've downloaded say
#include <library.h>

System header files
#include <iostream>

To compile the code, you would do something like
gcc -I/path/to/library prog.cpp

Where /path/to/library is the directory where library.h is located.

Of course, if you're using an IDE of some sort, you specify /path/to/library using some dialog or other.

My problem is sorted now.But I am left with some doubts.
Why we are using

Code:

#include"c:\anyfolder\anyfile.cpp"
instead of
#include"c:\\anyfolder\\anyfile.cpp"

quote:

Code:

You don't include CPP files, you only include libraries

Here I am having one file say time.cpp whose object i want to declare in other file.That's why i am including time file.Is there any other clean or more acceptable method?

Originally Posted by vaibhav

Here I am having one file say time.cpp whose object i want to declare in other file.That's why i am including time file.Is there any other clean or more acceptable method?

Yes, the proper method is to define the class in a header library, implement the class in the second file and include the header in both the main file and the implementation. Add the both to a project, compile and link.

Code:

// classProto.h

#ifndef CLASS_PROTO_H
#define CLASS_PROTO_H

class foo {
   public:
      foo(int);

      int getData() const;
      void setData(int);
   private:
      int Data;
};

#endif

Code:

// ClassImplement.cpp

#include "classProto.h"

foo::foo(int DATA = 0) {
   Data = DATA;
}

int foo::getData() const {
   return Data;
}

void foo::setData(int DATA) {
   Data = DATA;
}

Code:

// main.cpp

#include <iostream>
#include "classProto.h"

int main() {
   foo bar(2);
   bar.setData(5);
   std::cout << bar.getData();
   return 0;
}

Why we are using

Code:

#include"c:\anyfolder\anyfile.cpp"

instead of

Code:

#include"c:\\anyfolder\\anyfile.cpp"

It's best just to use forward slashes and forget about backslashes.

Code:

#include "c:/anyfolder/anyfile.h"

Doesn't front slash(/) refers to web address only?

pssst:

Code:

jshao@MCP ~/Programming/C++ $

here's a hint:

Code:

jshao@MCP ~/Programming/C++ $ uname
Linux

Doesn't front slash(/) refers to web address only?

Forward slashes are Linux and Unix's directory separators. The original web servers were Unix ones, so the web evolved around forward slash directory separators.

That is, in Windows, a path looks like this:

Code:

C:\windows\command.com

But on *NIX, a path looks like this:

Code:

/sbin/ifconfig

Most C functions, like remove, can take either forward slashes or backwards ones:

Code:

remove("..\\something");
remove("../something_else");

(C++ functions are the same way.) I actually prefer to use forward slashes, because you don't have to escape them.

For #includes, having a backslash is undefined behaviour. Sometimes "..\h" works, sometimes "..\\h", sometimes neither.

All told, it's best to just use forward slashes.