At 2:26 PM +0100 4/26/02, Nicholas Clark wrote:
>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}
Because, while you may run into problems fitting something in between
1.0000001 and 1.0000002, it's not a problem to fit something between
3 and 4. Floating point precedence is a problem at the edge, but
integer precedence makes things potentially difficult for user-added
operators if you want to fit things between the standard operators.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
