C++ Telephone Directory Program

[The Dark Knight]

avtar.xmbhost.com/c++/telephonedirectory.cpp

Made it the other day, does it work nice and fine for everyone?

Any suggestions or tips or something?

[tensuke]

Um how do I get it?I went to the page and it was code,and I went to the site(nice BTW) and couldn't find a link.
Is it just the code?Because if I'm just supposed to comment on the code,then it's great.
BTW,what's that font in your art museum sig pic,on the top?I've never known what that is...

[It's me again]

tensuke said:

Um how do I get it?I went to the page and it was code,and I went to the site(nice BTW) and couldn't find a link.
Is it just the code?Because if I'm just supposed to comment on the code,then it's great.
BTW,what's that font in your art museum sig pic,on the top?I've never known what that is...

You have to compile it.

---

I tried compiling it and got over 200 errors...o.0

[The Dark Knight]

I made it using Borland C++, and it shows no errors at all.

Stupid compiler differences. Did you use Turbo C++? Because I think that one has problems with the GOTOXY function.

[It's me again]

Dev-C++

[Bradley]

I got numerous errors with MS Visual C++ 7.1.

It doesn't like to refernce fstream.h directly; iostream seems to work better with it. just drop the .h part.

After the includes throw using namespace std; into the document so it doesn't complain about undefined functions cin() and cout().

It proceded to produce about 44 95 (now that I got fstream to load) errors on every use of finout, gotoxy, and clrscr.

This might help with some of your "problems": www.daniweb.com/techtalkforums/thread11430.html

You should upload a compiled version to, since compliers don't like you.

[J. Meeter]

From a friend:

Seems to have strange indentation, but I'll assume that it appears indented properly on your friend's editor.

1. The includes are old style C++. Latest standards would be:

#include <fstream>
#include <cstring>
#include <cstdio>
#include <cstdlib>
using namespace std;


2. Why is phone declared as long int in struct customer. Wouldn't a char array be better? Not that a long int wouldn't work, but if I specify a phone number that is "long enough", the phone number may be stored as a negative number (hint: long vs. unsigned long .

3. count could have been a local variable instead of global and could have been passed around to the other functions via pointer. Same with finout, which is also declared global.

[xubl]

Tar knows C++!

[David (Monty)]

Nice program

Had a little trouble compiling on GCC, but I finally did. Good work ;D

[The Dark Knight]

1. Thanks Monty.
2. Yes Zo, Tar knows C++.
3. IEYHO, Thanks for that. I'm using Borland C++ 5.02, we need to specify .h in them as header files. As for cstring and all that, I doubt header files change that much, but these are the standard header files. I'm sure your friends compiler uses a different style of header files that have certain alterations in them, or like some of mine, he's made some of his own header files. I've declared the phone number as long because some people might want to enter Country Codes in them as well, making them very large. I don't like using pointers.

4. CCWorld, Cin and Cout undefined functions? They're the basics of C++ and of the most basic file, IOSTREAM. Gotoxy is a print locator, useful for formatted outputs. Finout is a function I created for the file fstream so that I can handle my files. Clrscr is a clear screen function. Yeah, next time I might as well upload a .exe file.

Cheers. ;D

[David (Monty)]

avtar said:

4. CCWorld, Cin and Cout undefined functions? They're the basics of C++ and of the most basic file, IOSTREAM. Gotoxy is a print locator, useful for formatted outputs. Finout is a function I created for the file fstream so that I can handle my files. Clrscr is a clear screen function. Yeah, next time I might as well upload a .exe file.

When using the newer header files (without the .h in them, and cstring, cstdlib, etc.), things like cin, cout, endl, fstream, etc. are declared in namespace std, so you need to either fully qualify the names with std:: (std::cout, std::cin, std::endl, std::fstream, etc.), place "using namespace std;" after the list of includes, or place "using std::cout;", "using std::endl;", etc. after the list of includes. For example:

Method 1:
#include <iostream>

int main()
{
   std::cout << "Hello world" << std::endl;
   return 0;
}
Method 2:

#include <iostream>
using namespace std;

int main()
{
   cout << "Hello world" << endl;
   return 0;
}
Method 3:

#include <iostream>
using std::cout;
using std::endl;

int main()
{
   cout << "Hello world" << endl;
   return 0;
}

Namespaces help avoid name conflicts. I often use the first method, even though it's more typing, because it nearly eliminates naming conflicts.

The standard namespace contains a LOT of names. If you include just a few standard library files, and place "using namespace std;" under them, most of the good variable names will be unavailable to use for your own variables!

[The Dark Knight]

Isn't just:

#include <iostream.h>

void main()
{
cout<<"BLAH!";
}


So much simpler. lol.

[squalleh]

avtar said:

Isn't just:

#include <iostream.h>

void main()
{
cout<<"BLAH!";
}


So much simpler. lol.

No, you have to define namespaces. The cin, cout, and endl functions are all a part of the standard namespace. So, the proper way to use them is:


#include <iostream>

int main ()
{
     std::cout << "Boo!" << std::endl;
     return 0;
}


Of course, as mentioned above you could do a couple different things. One would be to define the standard namespace all together (example 1 at the bottom), or to define the specific functions (example 2).

---

Example 1

#include <iostream>

using namespace std;

int main ()
{
     cout << "Boo!" << endl;
     return 0;
}


Example 2

#include <iostream>

using std::cout;
using std::endl;

int main ()
{
     cout << "Boo!" << endl;
     return 0;
}

[It's me again]

I WANNA SEE IT!

^{someone compile it!}

[The Dark Knight]

I'll do it and upload the executable Prohibited.

Squall, my compiler accepts the program just as I wrote it, and even in my C++ classes, we're being taught hte way I just displayed...