Hi Przemek,
Il 19/10/2009 14.34, Przemysław Czerpak ha scritto:
[snip]
Pleas note that you requested about sth what depends on local preferences
rather then universal functionality. You want to extract time from
timestamp value as string in format "hh:mm:ss". I would preffer numeric
value comparable to second() results. Someone else may preffer string
in format "hh:mm:ss.fff" and someone else in format like "hh:mm:ss.ff"
(it's compatible with TIMETOSC()/SECTOTIME() CT3 functions)
HB_TTOD() job is simple and I'll add it but the second function seems
that should be implemented locally by user because it have to be tuned
to local preferences encoded in existing Clipper code.
I don't want to force anyone to use any time format ;-)
What I was thinking was an equivalent function for TIME() that is a
standard Clipper function also if surely will be useful both way: with
and without milliseconds.
[snip]
Probably, my thought, it will be useful to have a full set of functions
giving freedom to user to choice the best for him:
HB_TTOTIME( tTimeStamp [, <cTimeFormat>] ) -> cTime
HB_TTOSEC( tTimeStamp ) -> nSeconds ( equivalent to SECONDS() )
HB_TSDECODE( tTimeStamp, [ @<dDate> ], [ @<cTime> ] [,<cTimeFormat>] )
HB_TSDECODEN( tTimeStamp, [ @<dDate> ], [ @<nTime> ] )
HB_TSENCODE( <dDate>, <nTime> | <cTime> ) -> <tTimeStamp>
BTW:
HB_FUNC( HB_TTOD )
{
long lDate, lTime;
if( hb_partdt( &lDate, &lTime, 1 ) )
hb_retdl( lDate );
else
hb_errRT_BASE_SubstR( EG_ARG, 3012, NULL, HB_ERR_FUNCNAME,
HB_ERR_ARGS_BASEPARAMS );
}
Thank you, I have already seen it on SVN.
Best Regards,
Francesco
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
