Thread: pointer to a structure?

I need a poniter to each variable for the structure but it seems because i have made a loop around the stuct it won't let me pass any variables outside of the loop. ( i hope i have made sence), is there a way to pass variables outside of the loop using pointers? or is there another way?.

Code:

#include <stdio.h>
#include <iostream>
#include <fstream>

struct product
{
int item;
char des[256];
int qty;
};


int main(int itemN, int qtyN, char ans, int *b)
{


do {

char items[256];




cout<<"\nPlease enter the item description > ";
cin.getline(items,256);
cout<<"Please enter the item number >";
cin>> itemN;
cout<<"please enter the quanity counted >";
cin>> qtyN;

product descrip;
product *ptr;

descrip.item=itemN;
descrip.qty=qtyN;
descrip.des=items;
ptr=&descrip;

cout<<"\nThis is the data you have entered\n";
cout<<"\nItem description > "<< descrip.des;
cout<<"\nItem > "<< descrip.item;
cout<<"\nQuantity > "<< descrip.qty <<"\n";
cout<<"\nIs this correct (Y/N) > ";
cin>> ans;

cin.get();

cout<< ptr;

} while ( ans=='n' );


ofstream a_file;
a_file.open("stores.dat",ios::app);


 cin.get();
  return 0;

}

A variable you declare inside of a loop exists only inside the loop.

If you want every product object to exist after the loop is done you'll need to store them somewhere -- possibly an array or vector or map of products. Make sure you declare the container before the loop, and then insert each entry into the container inside the loop.

Originally Posted by Cat

A variable you declare inside of a loop exists only inside the loop.

If you want every product object to exist after the loop is done you'll need to store them somewhere -- possibly an array or vector or map of products. Make sure you declare the container before the loop, and then insert each entry into the container inside the loop.

Ok, well how do i store a memory address in an array?

Define your variables outside of the loop. Because they're defined in the loop, they only exist in the scope of the loop. When you leave the scope, the variables don't exist anymore. This is one of the reasons you're taught to define your variables at the top of a function.

Originally Posted by SlyMaelstrom

Define your variables outside of the loop. Because they're defined in the loop, they only exist in the scope of the loop. When you leave the scope, the variables don't exist anymore. This is one of the reasons you're taught to define your variables at the top of a function.

ok, but if i declare my variables before the loop how do i go back to change them if they are wrong?

You can still assign to the variables in the loop all you want. That has nothing to do with memory, as far as your concerned. Unless you're talking about resizing a dynamically allocated array, in which case you'd declare the pointer outside of the loop, and inside you'd both delete and reallocate it all you want.

Off topic, since I didn't really look at your code the first time around:

Code:

int main(int itemN, int qtyN, char ans, int *b)

main is not a function you can pass arguments to like that... the only time it accepts arguments are if they're through the command line, which these aren't. Like the other variables we've named, you'll want to define those at the beginning of the main function.

Originally Posted by SlyMaelstrom

You can still assign to the variables in the loop all you want. That has nothing to do with memory, as far as your concerned. Unless you're talking about resizing a dynamically allocated array, in which case you'd declare the pointer outside of the loop, and inside you'd both delete and reallocate it all you want.

Off topic, since I didn't really look at your code the first time around:

Code:

int main(int itemN, int qtyN, char ans, int *b)

main is not a function you can pass arguments to like that... the only time it accepts arguments are if they're through the command line, which these aren't. Like the other variables we've named, you'll want to define those at the beginning of the main function.

yea ok, i understand the first part

(after) oh, now i do see what you are saying, aswell as moving those variable (i hope my terminology is right)