[Mitgcm-support] RE: variable blabla

[mitgcm-support at dev.mitgcm.org]

Hello, hows Germany?
Surely timer_stats.F shouldn't be bothering Stpehanie
should it? i.e. it should not appear on other 
machines and then she wouldn't have to make it go 
away.

Also "blabla" doesn't seem like a very good name 
for a variable. Generally we have all been very
disciplined about using meaningful and informative
variable names. I don't think we should abandon that
approach. Maybe it means something in German?

Chris

-----Original Message-----
From: heimbach at mit.edu [mailto:heimbach at mit.edu]
Sent: Sunday, April 21, 2002 3:52 PM
To: Chris Hill
Cc: Support at Mitgcm.Org
Subject: Re: variable blabla


Not sure wheher this applies, but:
timer_stats.c is specific for the ibm sp3 wher it replaces tim.c
Maybe stephanie doesn't need/have to bother about this routine.
P.

Quoting Chris Hill <cnh at plume.mit.edu>:

> What is blabla anybody?
> 
> Chris
> 
> -----Original Message-----
> From: Stephanie Dutkiewicz [mailto:stephd at plume.mit.edu]
> Sent: Friday, April 19, 2002 11:00 AM
> To: Chris Hill
> Subject: compiler error
> 
> 
> 
> Hi Chris -
> I'm trying to compile c44 on lego (with mpi).
> Before (ie c38) I had to cc -c -64 tim.c to get it to work.
> Now there it complains about timer_stats being n32 not n64.
> But when I try cc -c -64 timer_stats.c I get the following
> error:
> lego:ocmip/bin % cc -c -64 timer_stats.c
> cc-1552 cc: WARNING File = timer_stats.c, Line = 11
>   The variable "blabla" is set but never used.
> 
>        clock_t blabla;
>                ^
> 
> cc-1552 cc: WARNING File = timer_stats.c, Line = 21
>   The variable "blabla" is set but never used.
> 
>        clock_t blabla;
> 
> 
> Any suggestions?
> Thanks
> steph
> 
> 
> 
>