atoi(text[0]) will not work because atoi expects a char*, not a char. That half of NeoKyrgyz's answer was basically useless and dumb.

If you want to convert the character "c" representing the...

You want to calculate the n-term series and not the infinite series?

Your "line equation" is wrong -- you have defined a point.

In that case, the right solution would still be to use the closed form expression :)

Well it's almost like the series for exp(x), except the signs are alternating and it's missing the x^1 term and the x^0 term has the wrong sign. If consider the series you get for exp(-x), you...

You want a struct with a double and a bool.

You should never use inheritance except as a mechanism for polymorphism -- one reason being that 'putting stuff into structs' or classes (a.k.a....

Maybe I'm not being very clear. I'm saying, suppose your class began with the following:

class dequeint {

private:
NodeType NodeArray[MAXSIZE];
int headi; // index of first...

Maybe some thinking would work, too.

This: ((tailsucci+1)%MAXSIZE) !=headi is wrong.

Figure out why.


One problem you have is that if tailsucci and headi are both equal, you can't tell whether the buffer is full or empty. You...

What the **** is wrong with you? The mechanism for creating datatypes in C++ is classes. Why wouldn't you use classes?

In the future, please keep your insanity to yourself. The insanity isn't...

The danger lurks because the pointer could be null, or the pointer could be pointing at something that no longer exists. It's easy for programmers to make mistakes like that. It's slightly harder...

It's the same thing -- once the code has been compiled -- and used for the same purpose. It's better to use the second way, passing "by reference," because the first desensitizes you toward...

Nope :)

It makes a copy of the string. For it not to do so would be counter-intuitive -- if it wanted a pointer to a string, it would ask for one.

In particular, you'll note that the constructor takes a...

Where you wrote ostream &Month::operator<<(ostream &strm, const Month &obj), you should be writing ostream &operator<<(ostream &strm, const Month &obj). The function you're defining is not declared...

The reason is that blah = 1 sets the lvalue blah to 1. You want blah == 1, which evaluates to true if blah is 1. It's generally a good idea in C++ to get in the habit of putting constants like 1 on...

Why do you have a class named Swap?

Flow charts are basically an awful way to design a program and an awful way to represent the design of a program. If you asked me to name any "good" ways to _represent_ the design, I couldn't. But...

Yes, we know what a static variable is.



I have no clue what you're talking about.

A better solution would just to make that variable a member of the class. Yours would require extra code to check that the same class is receiving the call as before. And it wouldn't be thread...

The ability to have static variables in the middle of functions is a crufty feature left over from the old days of C.

I'm guessing it would just act like a static variable. I wouldn't make use of it at all -- put any static constants you have in your class definition and don't use static variables.

Why do you say static variables will be disposed of at the end of the function call?

Well it seems you didn't read my reply, so never mind.

What the ****? Your random function isn't random any more.

Your problem is that you're recreating the file every time through the loop. Thus, the old data gets replaced.

One reason you can't just "catch and handle" pointer errors is that if you overwrite something in the wrong place of memory, it can totally screw with the behavior of your program. You could have...

Using pointers directly is undesirable because pointers are dangerous. If you have a pointer, the thing it's pointing to could become destroyed, so you have to make sure that hasn't been done. ...

Well, error catching is what try-catch blocks are for...

But if you're talking about some pointer-related bug, the right answer is to avoid using pointers directly in the first place. I don't...

Hm yes, VernonDozier identified what was actually causing your problem. Fix your random function, too, though.

Your function random is broken! This is an awesome bug. It's broken in two ways.

First, it's broken because rand() may return RAND_MAX. In such a case, your random function is clearly broken,...

Also, it's important to delete them because they might have other stuff to do (like flushing data to filehandles, and such).

It doesn't remain "in memory" because the process has completed and all of its memory is reclaimed by the operating system.

What the **** are you talking about? When the program ends, nothing remains.

Header files typically contain declarations of functions, not their definitions. Typically, the implementations are placed in a similarly named cpp file. Your project will then have multiple cpp...

This is absolutely awful. Do not do what you are talking about doing.

Tell us what your problem is, what you really are trying to achieve, instead of asking about one particular mechanical...

Maybe this is a stupid question, but why you writing myvector->push_back(...) instead of myvector.push_back(...)? myvector is a cliext::vector<T>, not a cliext::vector<T>^.

C# is easy to learn, and unless you have a very specific, articulable reason to be using C++/CLI, you would be better off going with C#.

Edit: Also, don't expect an answer here; your question is...

Yes, you can make your own class that inherits from ostream.

Why don't you just learn both?