Thread: headers and int main()

Originally Posted by lpaulgib

1. When I searched online for cstdlib, I got a list of functions and the explanation that it's for memory allocation and lists and sorts. Do I even need this in the program I'm using? The list of functions didn't show anything I use in that block of code.

The system() function is in there. system() is a function to be avoided, usually.

2. cstdio looks like something for input/output, but online referencing says it's formatted IO functions. Can someone elaborate for an idiot? Once again... I don't see how I need it in this program.

cstdio is completely unnecessary for this program.

3. ...int main(). I don't understand the (int nNumberofArgs, char* pszArgs[]) part. I searched the string on google, and got limited results. I was thinking maybe something to do with declaring an array or matrix with the [] brackets. Could someone explain this to me in a basic way. No need to go too deep. And once again..... Is this even necessary in this program?

No, it's not necessary in this program. And the reason your Google search didn't find anything is because those arguments are almost always called "argc" and "argv", not those silly names given here. Google "argc argv" and you'll get a ton of stuff.

4. And finally.... I took out the books original content to include using namespace std. I read somewhere online that this is inefficient, and so instead I did the other method above in the code. Am I looking at this in the right way, or is there a potential problem with my styling of the code?

It isn't inefficient. It does have some very important ramifications whether you use a "using" declaration or specify namespaces explicitly. Until you know enough to understand those ramifications, I suggest doing it the way you're doing it now and stay away from "using" declarations.

Given just what you've posted here, that book looks like a piece of garbage. Unfortunately I don't know what books are good alternatives.

Good critical thinking. Impressed.

Originally Posted by lpaulgib

So my first question is on the #include header part. I think I grasp the concept of what a header is. If I got it right, it's basically a list of definitions for commands I use? So the book isn't explaining to me when to use which one.

Altho the easiest thing to do may seem to be to ask about stuff like this on the forum, you are more likely to just waste more time that way (plus: that of others) than if you simply used the internet:

All about "C++ #include"

If you don't live in a city with a library, you may want to order another book, altho the Dummies books can be good so I am surprised they don't explain this.

3. ...int main(). I don't understand the (int nNumberofArgs, char* pszArgs[]) part. I searched the string on google, and got limited results. I was thinking maybe something to do with declaring an array or matrix with the [] brackets. Could someone explain this to me in a basic way. No need to go too deep. And once again..... Is this even necessary in this program?

In this program it is not necessary since you don't use it, however, let me be honest: there is absolutely ZERO chance that this is not discussed in a book with C++ on the cover. And I've seen that book around, it is at least 300-500 pages. You are mistaken, you just have not read enough yet. Look for sections on "program arguments". Basically:

int nNumberofArgs, an int, (most often called int argc, for "argument count") is the number of arguments provided to the program from parameters passed on the command line. This is always at least 1, since the first parameter is the name of the program.

char* pszArgs[], an array of char pointers (most often called char *argv[] -- evidently that book uses some kind of zany "Hungarian" notation), contains the value for each parameter. Here's a demo:

Code:

#include <iostream>

using namespace std;

int main(int argc, const char *argv[]) {
	int i = argc-1;

	if (argc > 1)
		while (i >= 0) cout << argv[i--] << endl;
	else cout << "No args\n";

	return 0;
}

Run this from the command line like this:

whateverprogramname this that 123

On one hand, you got what you paid for...

On the other hand, look ahead a little bit in the book. I have a C++ For Dummies book, though it has been collecting dust on a shelf for several years now because I found it rather frustrating. To be fair, this edition claimed to teach Windows programming which is why I bought it, but a little more research would have saved me that money and some frustration by buying the book I ended up getting instead.

Anyway, one of the things that I didn't care for was that the author would "slip new things" into his code examples without explaining them beforehand. Instead he would explain them later with an attitude of "I'm so witty for doing that".

A question about the code you posted: is the word "interger" the way the book spelled it? If not, then please note it should be "integer". If the book uses that spelling throughout however, then... wow.

Just addressing the use of command line args (int argc, char argv) the use of it depends on you and what you expect your target platform to be (Windows or everything else). The primary reason for implementing support for command line args is that in the UNIX way of thinking, all programs should be able to read the output of other programs as input and it should always output things in a clean manner so that programs can be chained together to solve larger problems. The dao behind this line of thinking is to create many small programs that do one thing well and use scripting to assemble these small programs into something that can solve larger problems/jobs. The UNIX programming mindset is explained a lot better in this free book, The Art of Unix Programming by Eric S. Raymond or ESR to our world.

Windows on the other hand not only doesn't subscribe to this model but discourages running things from the command line. As such, while it might seem more correct to do this everywhere, the fact is unless most of the apps running on your platform works in this fashion (and on Windows they do not), there is little value in you doing it. However if you think you might be coding on those other platforms (or making your code cross platform) then it is a good idea. Also if you are considering this, look into getopt. This comes with Linux and Mac but like everything else, it is missing on Windows though a Google search will show a Win32 work-alike. Getopt makes dealing with the command line way less work and the resulting code is cleaner too IMHO:

Code:

#include <getopt.h>

// supports -h (help), -i <input file>
#define CMDOPTS "hi:"

   string inputFile;
   opterr = 0;
   int c;
   while((c = getopt(argc, argv, CMDOPTS)) != EOF)
   {
      switch(c)
      {
	 case 'h':
	 {
	    Usage();
	    break;
	 }
	 case 'i':
	 {
	    inputFile = optarg;
	    break;
	 }
      }
   }