Keeping track of values without an array

In the function below, how can I keep track of factors. For every factor how could I store as a variable so that I can reference it later. The problem I have now is that every loop the value will change, so I will delete every factor and the variable will end up being the last factor, if any. Is there anyway to do this without an array or stuff covered in the second half of intro. computing courses?

Code:

---

void factorevaluation(int n)
{   

int count;
    count=2;
  storefactor1;
   
   
 
    while(count <= (n/2))
    {
    if (n%count==0)
    storefactor1=count;
    count++;
    }
 
}

---

sorry about that

edit your post so you have [/code] as the bottom tag not simplay [code].

No. Of course not. Your only option is to use an array, write them to a file for later analysis, or just print the values as they come down the pike. What else did you expect :confused:

>What else did you expect
magically_store_values_without_an_array() by including <iwish.h> of course.

>Is there anyway to do this without an array or stuff covered in the second half of intro. computing courses?
Make a bunch of variables to take the place of an array.

-Prelude

can't you just output each time the loop goes through before it goes again? kind of the same idea as:

Code:

---


for (int count = 1; count <=50; ++count)
{
cout<<"Count is "<<count<<". \n";
}

---

That would output 1 - 50.

Code:

---

void factorevaluation(int n)
{   

int count = 2;
 
  storefactor1;
   
   
 
    while(count <= (n/2))
    {
    if (n%count==0)
    storefactor1=count;
    cout<<storefactor1<<"\n";
    count++;
    }
 
}

---

yes you can, but if all you do is just output it to the screen you can't go back later and retrieve a particular value. You could write each value to a file in addition to/instead of writing to the screen, and then read/write to file as needed to avoid using an array (or some other container), but that's it. The stuff is either stored in memory somewhere(fast RAM memory using a container within the program, or slow memory using a file someplace), outputting to some device (screen, printer, whatever), or ignoring whatever comes down the pike.