Isn't this puzzling?

I intend to read several numbers into the array of X and then several others into the array of Z; however, it happens that the following codes can correctly read X but not Z. Only after I change the 'i' in the second loop to 'j' will both read correctly. This is the only 'for' loops in my function.

Code:

---

    for (int i=0; i<dimofX_model; ++i)
                {
                readfile>>temp.X[i];
        }
    //read in the X variables;
   
        for (int i=0; i<dimofZ_model; ++i)               
            {
                        readfile>>temp.Z[i];
                }
    //read in the Z variables

---

Hmm... I guess your compiler doesn't conform to the scoping rules of for statement initializations. Unless, I'm missing something.

What compiler are you using? It's odd alright.

Using VC6? It's probably what Sly says. Does this work as expected?

Code:

---

{
for (int i=0; i<dimofX_model; ++i)
{
  readfile>>temp.X[i];
}
}
//read in the X variables;
{ 
for (int i=0; i<dimofZ_model; ++i)               
{
  readfile>>temp.Z[i];
}
}
//read in the Z variables

---

Try this -

Code:

---

int i=0;

for (i=0; i<dimofX_model; ++i)
{
    readfile>>temp.X[i];
}

for (i=0; i<dimofZ_model; ++i)               
{
    readfile>>temp.Z[i];
}

---

and tell us if that works.

yeah, the last suggestion works. I'm using DevC++. Isn't that disturbing?

That's very odd. What version of Dev-C++ do you have? I wasn't aware of any for loop issues like VC6 has.

In any case, you might want to consider an IDE switch; perhaps to Code::Blocks or Visual C++ Express 2005. I believe there is no longer any active development in Dev-C++

Aye, 'tis very odd ... :/ Did you try it with a while() loop?

By the way, I forgot to say: after I changed it to 'j', compile it and it works; after that I changed it back to 'i', compile it and it works too. Is this helpful for tacking the issue?

> By the way, I forgot to say: after I changed it to 'j', compile it and it works

Perhaps you made other changes before this, and for some reason the project wasn't recompiled to reflect those changes. If I recall correctly, I used to have issues with Dev in this respect (making changes, hitting "Compile and Run," but not actually having the files compiled/linked)

You don't mean to say g++ contains bugs like these... JaWiB, the IDE has nothing at all to do with this issue.

Quote:

---

Originally Posted by JaWiB

> By the way, I forgot to say: after I changed it to 'j', compile it and it works

Perhaps you made other changes before this, and for some reason the project wasn't recompiled to reflect those changes. If I recall correctly, I used to have issues with Dev in this respect (making changes, hitting "Compile and Run," but not actually having the files compiled/linked)

---

This is obviously the case. If you don't use rebuild all sometimes the compiler will not reflect ALL the changes you made and saved earlier.

Yeah, sometimes a rebuild all is a good idea just to make sure everything is up to date.

Also, you could save the hassle of needing two for loops if you did something like this:

Code:

---

int i=0; // Could prob get rid of this and put it inthe for loop

for (i=0; i<dimofX_model; ++i)
{
    readfile>>temp.X[i];
    readfile>>temp.Z[i];
}

---

if you saved the file from which you're reading as follows -

Code:

---

XVar1 ZVar1
XVar2 ZVar2
XVar3 ZVar3
XVar4 ZVar4
XVar5 ZVar5
...
XVarN ZVarN

---

Obviously all the X and Y vars are numbers (I'm assuming). You don't even need them on new lines if you don't want to. I just thought I'd throw that out there.