News, download Xailer, Harbour and Mingw:
English: http://xailer.info/wordpress/en/?p=367
Spanish: https://xailer.info/wordpress/es/?p=1367
Existing for more than 14 years, Xailer is a professional and complete tool for developing applications with Harbour: ....
On 3/24/2019 8:21 AM, Hurricane wrote:
News, download Xailer, Harbour and Mingw:
English: http://xailer.info/wordpress/en/?p=367
Spanish: https://xailer.info/wordpress/es/?p=1367
Existing for more than 14 years, Xailer is a professional and complete tool for developing applications with Harbour: ....
Now that with virtualization and Cloud hosting, maybe no Clipper
applications need to be ported to other languages or platforms. :)
Forgot a problem: Year 2038 date problem. Old
Clipper applications are 16-bit? Or it is 32-bit?
Dear Mr. Man-wai Chang:
On Sunday, March 24, 2019 at 8:49:16 AM UTC-7, Mr. Man-wai Chang wrote:
...
Forgot a problem: Year 2038 date problem. Old
Clipper applications are 16-bit? Or it is 32-bit?
They use Windoze / DOS date format. Clipper's problem was Y2K, not old Linux date format.
David A. Smith
But Clipper for DOS is still 16-bit at best. Could a
16-bit integer handle dates beyond year 2038? You
need a 64-bit date....
Disclaim: I am not so sure about Clipper's data
structures. I am also not sure about the Command
Prompt of Windows.
Clipper does integer math for year, day, month, hour, minute, second,
stored as strings. The STORED date is truncated two two digits of year "assuming" what ever "century" is set for. So dates stored "last century" will have to lots of "guard code" to make them pertinent. Dates are very much controlled by the Windoze machines they run on, and Windoze was fixed before Y2K.
Hi David,
Clipper does integer math for year, day, month,
hour, minute, second, stored as strings. The
STORED date is truncated two two digits of year
"assuming" what ever "century" is set for. So
dates stored "last century" will have to lots
of "guard code" to make them pertinent. Dates
are very much controlled by the Windoze machines
they run on, and Windoze was fixed before Y2K.
The lupdate() field in the DBF header is truncated
to YYMMDD, but a date field in a DBF record is
always YYYYMMDD (D,8,0). However, if you use a
two digit year in the picture format for a date,
then Clipper will make assumptions about what you
are typing based on the SET EPOCH setting. So to
avoid problems with dates in "last century",
using a four digit year in the picture format is
a good idea.
Hi David,--
Clipper does integer math for year, day, month, hour, minute, second,
stored as strings. The STORED date is truncated two two digits of year
"assuming" what ever "century" is set for. So dates stored "last
century"
will have to lots of "guard code" to make them pertinent. Dates are
very
much controlled by the Windoze machines they run on, and Windoze was
fixed
before Y2K.
The lupdate() field in the DBF header is truncated to YYMMDD, but a
date field in a DBF record is always YYYYMMDD (D,8,0). However, if you
use a two digit year in the picture format for a date, then Clipper
will make assumptions about what you are typing based on the SET EPOCH setting. So to avoid problems with dates in "last century", using a
four digit year in the picture format is a good idea.
Regards,
Klas
--- news://freenews.netfront.net/ - complaints: news@netfront.net ---
But seeing we asking questions about how to
support Clipper in a new environment. Have you
considered X#?
http://xsharp.info
Dear Johan Nel:--
On Monday, March 25, 2019 at 4:57:21 PM UTC-7, Johan Nel wrote:
....
But seeing we asking questions about how toI am waiting until you finish the "on ramp" for (x)Harbour.
support Clipper in a new environment. Have you
considered X#?
http://xsharp.info
David A. Smith
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 113 |
| Nodes: | 8 (1 / 7) |
| Uptime: | 127:03:38 |
| Calls: | 2,501 |
| Files: | 8,692 |
| Messages: | 1,924,636 |