5 ms·

It can provide very fast performance on integer values, eliminating the need for a separate int type and avoiding the terrible errors than can result from int t

• ErsatzVerkehr 13y ago
  Integers are also exactly represented in the standard floating point formats, so this isn't even a particular advantage of DEC64. What is "int truncation" anyway? Overflow?
  • riffraff 13y ago
    I believe he means the stuff that happens in js like 111111111111111110000 + 1111 = 111111111111111110000; EDIT: not a javascript specific thing, rather a float one, methinks
    • chimeracoder 13y ago
      To clarify, they are basic floating-point errors from C that happen to be errors for integers as well in Javascript, because Javascript does not support fixed-precision integers.
• austinz 13y ago
  I know the author despises types, but sometimes types provide valuable semantic information. Like, indexing into an array using a float is completely unnecessary and meaningless.
  • jmpeax 13y ago
    It's not completely unnecessary and meaningless. In computer graphics, floating point indexing is used to interpolate between texel values during texture look-up.
    • austinz 13y ago
      Interesting. A weighed average between at least two values in an array? Makes sense in the context of computer graphics. Thanks for the correction.
      • MaulingMonkey 13y ago
        I don't typically think of it as indexing an array, but it's conceptually similar in some circumstances I suppose. The hardware still eventually has to read values from integer-based addresses, though. As to the details: Sampling modes customize how the value calculation is done. Some will simply round the index to the nearest integer texel, resulting in only one value being accessed (cheap.) Others will interpolate via weighted average as you're thinking, in the 1D case. Then there's the 2D and 3D cases... plus mipmaps... plus anti-aliasing patterns... at which point you could easily have 16+ samples bearing little resemblance to "indexing an array", especially as one can apply all these interpolation techniques to generic functions such as perlin noise which aren't array based.
        • tel 13y ago
          And each of those sampling methods is exactly a function Double -> Int Which is also exactly why having an int type is important. It otherwise becomes much harder to talk about the meaning of those functions.
• alextgordon 13y ago
  Why does anybody listen to Crockford? He wrote a human-readable data format but refused to give it comments. He wrote an obnoxious linter that bans continue;. Now he's proposing to replace integers with decimal floating point type (what happens if someone wants to store a 64-bit integer?). As a C programmer, he just seems off his trolley.
  • mark-r 13y ago
    How often have you needed a 64-bit integer where a 56-bit one wouldn't do? I rather like the idea of having only one numeric type.
    • alkonaut 13y ago
      Still, hardware is inherently base-2. What I'd like to see is hardware assisted adaptive precision predicates and compilers/runtimes that make proper use of modern instructions. I have never ever thougt that float/double/decimal was too much choice.
    • alextgordon 13y ago
      As a succinct example, 64-bits is 584 years of nanoseconds. 56-bits is only 2 years of nanoseconds. The problem is that many extant APIs return 64-bit integers, so if your language only has 56-bit integers you are creating a bug/vulnerability every time you want to talk to the outside world. e.g. sqlite has sqlite3_column_int64() to get a value from a result set. How do you use that safely if your language can only do 56-bit ints? Ugly. Remember the "Twitter Apocalypse" when Twitter changed their tweet IDs to be bigger than 56-bits and all the JS programmers had to switch to using strings? Also, bitboards. Bitboards are cool: https://chessprogramming.wikispaces.com/Bitboards https://chessprogramming.wikispaces.com/Bitboards. EDIT: I also reject the premise that just because there's an ugly hack available, we can get rid of useful language features. Am I working for the language or is the language working for me?
      • mark-r 13y ago
        The question is, why do APIs return 64-bit values? In general it's not because they need all 64 bits, it's because the 64-bit integer type is convenient for them. This might make Crockford's proposal completely impractical but it doesn't invalidate the argument that led to it. I reject the nanosecond example because it's completely arbitrary. 64 bits of picoseconds would only cover 0.584 years so should we claim 64 bits isn't enough? Wouldn't 2000 years of microseconds in 56 bits be good enough? I'll give you credit for bitboards though, that's one I hadn't considered.
• PeterisP 13y ago
  I do not see any basis for the statement 'very fast performance on integer values', given that simple calculations like substraction and checking of simple equality require many operations in the proposed standard.