[fpc-devel] 3.0.4 and Windows 64
ozznixon at gmail.com
Sun Oct 7 15:39:04 CEST 2018
Thank you very much sven! This is old code, and uses Extended and Comp, so
the xBase files are byte for byte compatible with Visual FoxPro. Most of
xBase is ASCII, However, uSoft in their wisdom started storing binary
formats when they bought out FoxBase and said, 20 byte ASCII or 4 byte
binary - xBase was not designed to be small, but, to be platform, CPU, and
programmer friendly. And decades later, we see something Microsoft screwed
up, and has dropped support for anyway (dropping FoxPro).
On Sun, Oct 7, 2018 at 8:56 AM Sven Barth via fpc-devel <
fpc-devel at lists.freepascal.org> wrote:
> Am 03.10.2018 um 14:23 schrieb Ozz Nixon:
> Thank you for explaining. Since I am needing compatibility at the disk
> level (binary form)... does anyone know of a unit or some routines to
> read/write: Comp, Double, Extended byte for byte the same? (even if it
> translates to something different at run time or in the dataset). If it was
> for the fact I maintain Halcyon (xBase) code I would slap this all in a DB
> server. Which also means my port of Accuracer (aidaim.com) is also going
> to have similar problems. :-(
> You can use FPC's softfpu unit though it is not compiled for all targets
> currently. But you can copy it from $fpcdir/rtl/inc/softfpu.pp and compiler
> yourself. Then you can use the type tfloat80 which is essentially Extended
> on which you can also use the operations defined in the softfpu unit (for
> convenience you could add a unit with operator overloads).
> Please note that Double is always the same on the main platforms and thus
> doesn't need special handling.
> fpc-devel maillist - fpc-devel at lists.freepascal.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fpc-devel