Furthermore, to do the 'logB' and 'scaleB' operations I want to say:
     x.exponent                  // logB(x)
     x.exponent += n        // scaleB(x,n)

Instead of the slow code which follows (sorry about the length):

++++code here++++

IEEE.logB = function (x)
{
 x = +x;         // guard against non-numerics

 var m, e;
 var abs = (x >= 0)? x : -x;             // don't care about -0!

 // calculate the approx exponent;
 // then fix the exponent estimate by computing the significand
 // (also works for pow() overflow/underflow!)

 e = Math.floor( Math.log( abs ) / Math.LN2 );

 m = abs / Math.pow( 2, e );           // don't care about NaNs!
 if (m >= 2)  e += 1;
 if (m <  1)  e -= 1;

 return e;
};

IEEE.scaleB = function (x,n)
{
 x = +x,  n = +n;     // guard against non-numerics

 // handle NaN, infinities, zeroes

 if (isNaN( x/x ))  return x;

 // multiply x by 2^n, first taking care for large |n|

 if (isFinite( n )) {
   while (n > 1023  &&  1/x != 0) {
     x *= Number.MAX_POWTWO;
     n -= 1023;
   }
   while (n < -1022  &&  x != 0) {
     x *= Number.MIN_NORMAL;
     n += 1022;
   }
 }
 return x * Math.pow( 2, n );
};

--------------------------------------------------
Technically you don't even need typed arrays to do it; it's just more work to implement a "pure" library that extracts the bit strings. With typed arrays it was utterly trivial (though you have to be slightly careful to avoid writing unportable code.)

FWIW.

Dave

On Mar 21, 2012, at 12:00 AM, Brendan Eich wrote:

Not gonna change number (the primitive type) to IEEE 754r DFP (not sure you were getting at that in closing). Just FTR.

These Number.prototype getters can be implemented today in top browsers (thanks to typed arrays) and in ES6 (binary data embraces and extends typed arrays). See https://github.com/dherman/float.js/.

/be

Roger Andrews wrote:
Floating-point numbers are formed of a sign (s), significand (m), exponent (e), and radix (b):
   (-1)^s * m * b^e
where 0<=m<b.

Often we want to access the s-m-e values directly, especially the significand. Notably when doing comparison for approximate equality by "masking out" the rounding error in the low order bits; or some multiprecise work. In ES5 this is painful.

The sign, significand, exponent, radix are intrinsic properties of a Number (like the length of a String) - so how about exposing them as properties of Number? Say the sign, significand, and exponent could be read-write and the radix read-only.

Advantages:
1)  extracting the significand is easy:
      x.signif
2)  scaling is easy (scaleB operation):
      x.exponent += N
3)  the logB operation is easy:
      x.exponent

Also programmers could distinguish a binary value from a decimal without using typeof, using the 'radix' property instead. This might future-proof against the possible coming of a Decimal type without breaking existing code. Does it help there?
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to