Code runs. Code reads in data. Code runs elaborate curve fits, parametric models, calculates useful parameters. Code then writes the input parameters to the output file, instead of the output data.

Of course, I only notice this after the code runs.


Published in: on August 7, 2003 at 17:00  Comments (3)  
Tags: ,


  1. That’s ok, I’ve discovered that my compiler thinks that I have two variables with the same name. It’s quite fun, too.
    bool made_repairs = false;
    //nested 3 ifs deep:
    made_repairs = true;
    return made_repairs;
    The address of the variable changes between setting it true, and the return. I don’t get it.
    Aren’t computers fun!?

  2. Could it be a scoping issue? You might have accidentally stuck a “bool made_repairs” somewhere inside one of the if’s, so the compiler defined a new symbol with the same name in that limited scope, and set it to true instead of the original.
    (Yes, I’ve been doing a lot of C++ lately. Does it show? 🙂

  3. No, it’s not that simple (I’ve already checked that). But it’s a template function, instantiated multiple times within the same calling function, and I really don’t trust the MS DevStudio C++ compiler any farther than I can throw it.
    And I don’t know intel assembly well enough to go into the assembly, and see what the hell the compiler actually did.

Comments are closed.

%d bloggers like this: