Thread: Functions Problem

I'm not sure man. My professor is kind of strange. He demands we use const double SENTINEL = 000000

Code: input >> name >> tempNum; while (!input.eof()) { if (parkingSticker == tempNum) { returnValue = name; break; } else if (parkingSticker != tempNum) { input >> name >> tempNum; } } A better way to write this would be: Code: while (input >> name >> tempNum) { if (parkingSticker == tempNum) { returnValue = name; break; } } Another improvement I could think...

Quote: Originally Posted by Ruined Embrace You guys see any corrections I could make to this? Not corrections, but a misunderstanding of what a double means: Code: const double SENTINEL = 000000; Those extra 0's do nothing except wear out your keyboard. This is exactly the same as this: Code: const double SENTINEL = 0.0; Why is SENTINEL a double anyway? Since target is an int, then SENTINEL should be an int. Regards, Paul McKenzie

Just a note. It's generally not a very good idea to compare floats and doubles for equality using ==.

I suppose that if you were not concerned about trying for a single point of return, the returnValue variable could be easily eliminated: Code: while (input >> name >> tempNum) { if (parkingSticker == tempNum) { return name; } } return "NOT FOUND";

I'm not sure man. My professor is kind of strange. He demands we use const double SENTINEL = 000000

Code: input >> name >> tempNum; while (!input.eof()) { if (parkingSticker == tempNum) { returnValue = name; break; } else if (parkingSticker != tempNum) { input >> name >> tempNum; } } A better way to write this would be: Code: while (input >> name >> tempNum) { if (parkingSticker == tempNum) { returnValue = name; break; } } Another improvement I could think...

I suppose that if you were not concerned about trying for a single point of return, the returnValue variable could be easily eliminated: Code: while (input >> name >> tempNum) { if (parkingSticker == tempNum) { return name; } } return "NOT FOUND";