Fwd: [sldev] Verified the lexxing bug in indra.l

[Jesse Malthus]

Forwarding on to list. (GMail users, make sure you click "Reply to
all" when replying to the list.)

---------- Forwarded message ----------
From: Strife Onizuka <blindwanderer at gmail.com>
Date: Jan 23, 2007 5:39 PM
Subject: Re: [sldev] Verified the lexxing bug in indra.l
To: Jesse Malthus <JesseMalthus at gmail.com>


I've submitted a few patches to JIRA with regards to the parsing of
LSO. Would be good if someone would look them over... (believe it or
not, first time making patches).

I hope they adopt your patches, they look good.


On 1/23/07, Jesse Malthus <JesseMalthus at gmail.com> wrote:
> By all means, please file a bug in JIRA (http:\\jira.secondlife.com\)
>
> On 1/23/07, Argent Stonecutter <secret.argent at gmail.com> wrote:
> > This script parses successfuly in LSL and produces an obviously
> > incorrect result.
> >
> > default
> > {
> >      state_entry()
> >      {
> >          llSay(0, (string)(3.-4));
> >      }
> > }
> >
> > [14:09]  Object: 3.000000
> >
> > This is what I suggested would happen in my previous article with the
> > constant folding patched for indra.l and indra.y.
> >
> > What's happening is that floating point numbers match an expression
> > that begins with {D}+"."{D}*, and {D} expands to [-]?[0-9], which -4
> > matches...
> >
> > This could be fixed in indra.l, but really folding '-' FP_CONSTANT
> > into FP_CONSTANT should be done in indra.y, because it keeps "a-1"
> > from matching this rule:
> >
> > expression : expression '-' expression ;
> >
> > Since "a-1" lexes to IDENTIFIER INTEGER_CONSTANT, not IDENTIFIER '-'
> > INTEGER_CONSTANT.
> >
> > See my previous post for the patch.
> > _______________________________________________
> > Click here to unsubscribe or manage your list subscription:
> > /index.html
> >
>
>
> --
> --Jesse
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>



-- 
--Jesse