On Tue, Apr 23, 2002 at 01:25:15PM -0400, Dan Sugalski wrote: > At 12:36 PM -0400 4/23/02, Buddha Buck wrote: > >OK, but that limits you to the, um, 24 standard levels of > >precedence. What do you do if you don't think that that's enough > > Internally precedence is going to be stored as a floating-point > number. Dunno how it'll be exposed at the language level, but at > least there'll be more than just 20 or so levels. Why store precedence as floating point rather than integer? [Or did I miss a design document} It would give the warm fuzzy illusion that I could always add another layer at 1.0000000025 between 1.000000002 and 1.000000003 but in practice surely there will be a nasty surprise as the implementation dependant limit on floating point accuracy bites and two levels that I thought were different were actually the same. And what happens if I set precedences of -0, Inf or NaN? [Or failing that whatever HUGE_VAL evaluates to?] Nicholas ClarkThread Previous | Thread Next