Jump to content

Talk:Microsoft Binary Format

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Cyberbot II (talk | contribs) at 08:15, 31 May 2016 (Notification of altered sources needing review #IABot). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing C‑class Mid‑importance
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
CThis article has been rated as C-class on Wikipedia's content assessment scale.
MidThis article has been rated as Mid-importance on the project's importance scale.

What is still missing

Important dates:

 Done 1975 = First release of Altair BASIC with (now MBF) floating point by Monte Davidoff who had some experience writing floating point routines

 Done 1978 = TRS-80 Level II BASIC introduces double precision

 Done 1980 = Intel 8087 with (now IEEE) floating point by William Kahan

 Done 1985 = IEEE standard published

1987 = QuickBASIC 4.00 (with IEEE floating point)

1991 = Visual Basic 1.0 (maybe not as important)

Conceptual:

 Done Why is IEEE different? Try to motivate existence of NaNs, infs, denormals, different exponent size.

 Done Why was it important for Altair BASIC to have floating point routines?

Why did Microsoft switch to IEEE after the standard was published, rather than sticking to MBF? (Interoperability, speed)

How would using these floating point numbers work from the user's perspective? What would you type, what would display?

What could you do with these floating point numbers?

 Done Did other software support MBF numbers? (MASM comes to mind; Multiplan for the Tandy 200 notably didn't, it used BCD)

Niceties:

A few examples could be enlightening, for example a few simple numbers and the corresponding bytes, a BASIC session demonstrating their use, anything to make it all a bit more grounded. It's a bit abstract as it stands.

Nicer looking diagrams.

— Preceding unsigned comment added by 82.139.82.82 (talk) 01:37, 2 October 2015 (UTC)[reply]

More potential To-Dos:
  • Check the number of decimal digits supported by the 40-bit and 64-bit formats. (Some sources state that the 40-bit format supports 9 digits, but it could also be an 8-digit format only.)
  • The references should be converted into the Template:Cite format and various parameters added.
--Matthiaspaul (talk) 22:56, 31 January 2016 (UTC)[reply]

Hello fellow Wikipedians,

I have just modified one external link on Microsoft Binary Format. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—cyberbot IITalk to my owner:Online 08:15, 31 May 2016 (UTC)[reply]