/prog/ - Programming

Your code is so fucking ugly. It took me a minute to figure out what was wrong, then I laughed and said, "That's what I would expect".

Basically, your block structure is wrong. C++ is not Python: white space doesn't mean shit.

>>3790

There is only one place in your code where you could have fucked it up: the while loop.

	while(getline(file_2open,holder));
		temp += holder + "\n";

This reads every line of the file and then stops at the last line, adding the last line, and only the last line, to temp.

What you want is:

	while(getline(file_2open,holder))
		temp += holder + "\n";

or, maybe

	while(getline(file_2open,holder))
        {
		temp += holder + "\n";
        }

Fucking Pythonfags.

>>3792

It's a great example of why you should never write it either his way or the way you suggested - it's so easy to accidentally leave a stray line terminator in that changes the logic. A better style is

while(...) {

as it resists these types of bugs (which are actually rather common in real code by good programmers). People get super stubborn about this even though this style is objectively better due to the lowered error rate. It's also a good example of why python got it (mostly) right with its spacing.

>>3795

> this style is subjectively better

> FTFY

If you use Allman style and always use braces, even when there is only one statement, then you don't make these sorts of errors.

The first thing you should do is fix all warnings and then quickly go fuck yourself for not using plain C.

Also write in some if statements to check whether or not you variables actually have any /value/.

guday m8

>>3795

Or you could format code in a decent way and not be a retard/faggot.

If you are used to writing shit this way you shouldn't have errors. It also makes you look 1337 as fuck.

>>3792

Never Python. Not even once.