Leopold Toetsch wrote:
>
> Anyway:
> - are there platforms with quad precision floats out there?
Several documents refer to quad precision hardware, but I can't find direct
references to any.
> - or should 12 byte long doubles get converted to 8 byte IEEE doubles.
Perhaps the following quote f
From: Bryan C. Warnock [mailto:[EMAIL PROTECTED]]
> On Tue, 2003-01-28 at 17:12, Garrett Goebel wrote:
> >
> > There are 3 standard binary IEEE 754 derived formats:
> >
> > Single Precision: 4 bytes
> > Double Precision: 8 bytes
> > Quadruple Precision: 16 bytes
>
> Actually, Quads
On Wed, 2003-01-29 at 04:56, Nicholas Clark wrote:
> On Wed, Jan 29, 2003 at 06:53:25AM +0100, Leopold Toetsch wrote:
> > Garrett Goebel wrote:
>
> > Many thanks for the links (searching for this stuff is a pain, there are
> > too many results ;-)
> >
> > Anyway:
> > - are there platforms with q
On Tue, 2003-01-28 at 17:12, Garrett Goebel wrote:
> Leopold Toetsch wrote:
> >
> > - 8/12 byte float issues are still the same - are these
> >formats really portable, or should we try to store
> >ASCII equivalents?
>
> No?
>
> ? Because my knowledge here approaches zero, so I'm just ap
On Wed, Jan 29, 2003 at 06:53:25AM +0100, Leopold Toetsch wrote:
> Garrett Goebel wrote:
> Many thanks for the links (searching for this stuff is a pain, there are
> too many results ;-)
>
> Anyway:
> - are there platforms with quad precision floats out there?
sparc Solaris and Irix both have 1
Garrett Goebel wrote:
Leopold Toetsch wrote:
>
> - 8/12 byte float issues are still the same - are these
>formats really portable, or should we try to store
>ASCII equivalents?
No?
? Because my knowledge here approaches zero, so I'm just aping
information back at you from google se
Leopold Toetsch wrote:
>
> - 8/12 byte float issues are still the same - are these
>formats really portable, or should we try to store
>ASCII equivalents?
No?
? Because my knowledge here approaches zero, so I'm just aping information
back at you from google searches and scanning documen
So more changes in packfile and related files, including:
- all packfile segments share a common header which is effectively
the format of a byte_code segment
- all packfile segments conforming to this format are unpacked with
the default_unpack routine, which just sets up a pointer to
the d
