+1
Brgds,
Viktor
On 2008.09.22., at 2:34, [EMAIL PROTECTED] wrote:
It's expected behavior. These are two different functions
and each of them use __TIME__ macro. So in the above test
you have information when common/hbverdsp.c was compiler
and when common/hbver.c
That's all. If it's a real pro
>It's expected behavior. These are two different functions
>and each of them use __TIME__ macro. So in the above test
>you have information when common/hbverdsp.c was compiler
>and when common/hbver.c
>That's all. If it's a real problem then I can change hb_verBuildInfo()
>function to not use __DAT
On Sun, 21 Sep 2008, [EMAIL PROTECTED] wrote:
Hi Toninho,
> Very strange, but this problem appeared again in latest SVN:
> harbour /build = 20:19:11
> ? hb_builddate() = 20:19:10
> Anybody confirm please ?
It's expected behavior. These are two different functions
and each of them use __TIME__ ma
HI ppl,
Very strange, but this problem appeared again in latest SVN:
harbour /build = 20:19:11
? hb_builddate() = 20:19:10
Anybody confirm please ?
TIA and best regards,
Toninho.
__
Faça ligações para outros computadores com o novo Yahoo! Messen
>My latest Harbour.exe /build display time 1 second more than
>hb_buildDate()
>
>harbour.exe /build = 21:24:09
>hb_buildDate() = 21:24:08
Now is fixed, thanks.
Toninho.
___
Yahoo! Mail - Sempre a melhor opção para você!
Experimente já e veja
Hi,
My latest Harbour.exe /build display time 1 second more than
hb_buildDate()
harbour.exe /build = 21:24:09
hb_buildDate() = 21:24:08
Don't ask me what I did to see this ;)
Regards,
Toninho.
___
Yahoo! Mail - Sempre a melhor opção para