[Numpy-discussion] float128 in fact float80
Sun Oct 16 17:16:13 CDT 2011
On Sun, Oct 16, 2011 at 3:04 PM, Matthew Brett <firstname.lastname@example.org> wrote:
> If we agree that float128 is a bad name for something that isn't IEEE
> binary128, and there is already a longdouble type (thanks for pointing
> that out), then what about:
> Deprecating float128 / float96 as names
> Preferring longdouble for cross-platform == fairly big float of some sort
I understand the argument that you don't want to call it "float80"
because not all machines support a float80 type. But I don't
understand why we would solve that problem by making up two *more*
names (float96, float128) that describe types that *no* machines
actually support... this is incredibly confusing.
I guess the question is, how do we deprecate a top-level name inside
the np namespace?
> Specific names according to format (float80 etc) ?
This part doesn't even seem necessary right now -- we could always add
it later if machines start supporting multiple >64-bit float types at
once, and in the mean time it doesn't add much. You can always use
finfo if you're curious what longdouble means locally?
More information about the NumPy-Discussion