Re: 0.94 will appear soon

[aeriksson2]

> clock_per_tick is declared as "static" but not given a constant value. 
> But as it is "static" it is therefore automatically given a value of 0. 
> So, it is in fact a definition, I.E. It is automatically give a value of 
> 0 (unless specifically given a different value) the first time one calls 
> the function containing it.
> 
> i.e. static unsigned long clocks_per_tick;
> is exactly the same as
> static unsigned long clocks_per_tick = 0;
> 
> So, no fix necassary.
> 
> Cheers
> James

Ah, right. Now that you mention it, I should have known. The binary 
actually gets 4 bytes smaller since it ends up in the bss instead of 
data data segment, right?

Thanks for setting me straight! Btw, do you know the maintainer of 
the code?

/A