[FLASH-USERS] Big Problem??

[Nathan Hearn]

P.S., I just realized that I may have confused things a bit.  (Sorry!)
 I am actually referring to variables used in the Fortran code, and
not the Flash parameters declared in Config.

- Nathan


On 8/4/08, Nathan Hearn <nhearn at uchicago.edu> wrote:
> Hi Seyit,
>
>     An uninitialized variable is one that is declared (specified as
> integer, real, etc.), but not assigned a value.  Thus, an
> uninitialized variable usually has whatever value was in its memory
> location before it was declared.  (It could be a random number,
> "infinity," or just garbage.)  If this variable gets used before a
> value is assigned to it, strange behavior may result, which would be
> very compiler- and architecture-specific).  If you are using
> uninitialized pointer or allocatable variables, the effects can be
> quite drastic and hard to identify.
>
>     Generally speaking, it is a good idea to assign a value to every
> variable soon after it is declared, even if it is only a temporary
> value that is not actually used.  (As I recall, there is a way to
> assign a null value to pointers, which is also a very useful
> practice.)
>
>
> - Nathan
>
>
> On 8/4/08, Seyit Hocuk <seyit at astro.rug.nl> wrote:
>> Hi Paul, hi Nathan,
>>
>> First of all; using --with-default-api-version=v16 when configuring
>> hdf5-1.8.1 works fine. Thanks for that Paul.
>>
>> Nathan, if you mean by uninitialized that the types are not defined
>> (like in config file REAL or INTEGER or whatever), then no because I
>> define them all. But if you mean I have included modules or parameters
>> which I don't use, that's correct and I am no expert in programming so
>> it might indeed be good to check this.
>>
>> Greetz,
>> Seyit
>


-- 
Nathan C. Hearn
nhearn at uchicago.edu

ASC Flash Center
Computational Physics Group
University of Chicago