07-18-2022, 07:10 PM
QB64 has two different encodings: MKD$, CVD and MKDMBF$, CVDMBF,
I tried them out on the same number and MKD$ is not the same as MKDMBF$.
When I wrote my programs, I think I had the default in QB set to MBF but the default in QB64 is IEEE so the MKDMBF$ etc. appears to be for backward compatibility with the QB /MBF option
Found this in WIKI:
"By the time QuickBASIC 4.00 was released,[when?] the IEEE 754 standard had become widely adopted—for example, it was incorporated into Intel's 387 coprocessor and every x86 processor from the 486 on. QuickBASIC versions 4.0 and 4.5 use IEEE 754 floating-point variables by default, but (at least in version 4.5) there is a command-line option /MBF for the IDE and the compiler that switches from IEEE to MBF floating-point numbers, to support earlier-written programs that rely on details of the MBF data formats. Visual Basic also uses the IEEE 754 format instead of MBF."
As always, Thanks for your time on this.
Arnold
I tried them out on the same number and MKD$ is not the same as MKDMBF$.
When I wrote my programs, I think I had the default in QB set to MBF but the default in QB64 is IEEE so the MKDMBF$ etc. appears to be for backward compatibility with the QB /MBF option
Found this in WIKI:
"By the time QuickBASIC 4.00 was released,[when?] the IEEE 754 standard had become widely adopted—for example, it was incorporated into Intel's 387 coprocessor and every x86 processor from the 486 on. QuickBASIC versions 4.0 and 4.5 use IEEE 754 floating-point variables by default, but (at least in version 4.5) there is a command-line option /MBF for the IDE and the compiler that switches from IEEE to MBF floating-point numbers, to support earlier-written programs that rely on details of the MBF data formats. Visual Basic also uses the IEEE 754 format instead of MBF."
As always, Thanks for your time on this.
Arnold