HP3000-L Archives

April 1999, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Fri, 30 Apr 1999 16:27:05 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Mike Yawn writes:

> TurboIMAGE databases (which may be what you're referring
>  to when you say 'how numbers are stored' provides both an IEEE format
>  and a Classic format.  I have no idea the relative usage of these
>  formats in the 'real world'.   There is also an intrinsic
>  (HPFPCONVERT?) to convert between the two formats.

Because the vast majority of all databases in current use were designed
before the implementation of IEEE reals on the HP3000, the HP real number
format must still represent at least 95% of all real number usage in IMAGE,
summed over all HP3000s.

Databases designed now should only use the IEEE real format -- and like all
changing standards -- the IEEE format will someday dominate usage. It's just
going to take a little while (probably longer than anyone thinks). Databases
are the most permanent (and unchanging) form of software on any machine, and
that's particularly true if the machine itself is a reliable workhourse --
like the HP3000 -- that can go on for years with no requirements for
replacement, redesign or recompiles.

This inability to change horses in midstream is an unintended consequence of
the "Curse of Good Design". A few good major "re-engineering" efforts every
few years -- as is often necessary with other platforms -- and HP real
numbers would soon be a distant memory.

As it is, unfortunately, HP real number usage is probably going to outlive us
all.

Wirt Atmar

ATOM RSS1 RSS2