Thread: Where do they go?

Cool thanks for the info I will read up on stacks now. Its a new term for me. I know that obviously this wouldn't be a solid foundation to lay a program on. The only reason I coded the example is I wanted to take the scientific approach to what I was told and prove it true. To my surprise I found this case to allow it to be recalled, but I noticed if the cout were repeated on the next line then the number came back different, but consistently different. I.E. When I first compiled it I used the loop control 10. Then I changed the control to see if it would cout other numbers and it did, but if I call it again then it reverted back to that original 10 and it did that EVERY time. I found that to be strange. I started a new project to see if I compiled it the first time and it was at a different loop if this would carry over as a new default, and it didn't. So strangly 10 is the default value for that memory adress if it isn't curry being used.

Last note if I changed the

Code:

cout<<*ptx<<endl;

to

Code:

cout<<pts<<endl;

it couts what I'm guessing is that memory positions hex adress which no matter what I change in the program that cout is consistent and true, just not always the same value stored in that adress. Thanks again for the information on the subject. I've been having problems really wrapping my head around pointers and how they are used so I'm constantly playing around with experiments.

@ brewbuck yea I'm starting to notice that. When I start getting above 5,000 lines of code in a program, I tend to create bugs if I'm not really careful(obviously becuase I'm still new to this) . So I started on a trek of learning why and how bugs are being created so that I could solidify the foundations of my programs allowing ultimately more complex programs for me to write and still trust.