|
PureBytes Links
Trading Reference Links
|
So if there is so much concern, let's zoom in on the Y2K issues
regarding TS.
The Server
internal: no problem, Gregorian date format
external: maybe problem with datafeed, if feed sends yymmdd
importing/exporting data: importing of 'yy/mm/dd' is a problem
Charting
uses the server
Easy Language
uses the server
So the problems are with datafeeds that send dates in "yy"
format, and with importing data in "yy" format.
The solution:
Roughly three functions:
One that determines if the data is in 'yy' or in 'yyyy' format.
If the data is in 'yy**" a warning should be given that "date
format is not YK2 compliant, only dates between for instance 1920 and
2020 are processed correctly, where '00' - '20' will mean 2000 -
2020.
The next function does the conversion from 'yy' to gregorian.
The third function does the conversion from 'yyyy' to gregorian.
Should be a breeze to write for Omega. So unless there are
other problems with TS internal date calculations we should not have
to worry.
Please correct me if I'm wrong,
Regards,
---------------------------
Guus Prick
Bird sings, cat awakens
http://www.iaehv.nl/users/guus/
---------------------------
|