simonmar:
> On 12 May 2006 00:47, John Meacham wrote:
>
> > On Thu, May 11, 2006 at 02:57:30PM +0100, Simon Marlow wrote:
> >> On the other hand, keeping intermediate Doubles to 80-bit precision
> >> is both (a) non-portable and (b) unpredictable (the programmer
> >> doesn't know which intermediates are going to be stored in 80 bits,
> >> and turning on optimisation will probably make a difference).
> >
> > Indeed, not storing the intermediate values as 80 bits is one of the
> > 'nicer' things I was refering to. :)
> >
> > though, this does bring up another standardish C type we should
> > support
> >
> > __float128
> >
> > and __complex as pointed out by Aaron.
> >
> > any idea what would be a good module to export them from?
>
> How standard are these? Foreign.C.Types is the obvious place, but it
> wouldn't be a good idea for that module to contain optional parts of its
> interface.
Especially since even:
checking Haskell type for intmax_t... not supported
checking Haskell type for uintmax_t... not supported
aren't universal :)
-- Don
_______________________________________________
Haskell-prime mailing list
Haskell-prime@haskell.org
http://www.haskell.org//mailman/listinfo/haskell-prime
