Re: Getting rid of backups in flex.

I think the problem arises between the lines:
> [-+]?{DIGIT}*"."{DIGIT}+{EXP}? | (line 7)
    and
> [-+]?{DIGIT}*"."{DIGIT}+{EXPERR}? | (line 11)
    cause of the last "?" mark. It means that this lexical sequence may be
found or not. In the case the sequence is not found, there is no way to
find a difference between the two rules which are exactly equal to the
following:
[-+]?{DIGIT}*"."{DIGIT}+
    So, I think, flex can not choose between the two different actions.


"Robert Minsk" <robertminsk@yahoo.com> a écrit :


> Given the following rules I am still getting 1 backup I'm trying to get
> rid of.
>
> DIGIT [[:digit:]]
> EXP [Ee][+-]?{DIGIT}+
> EXPERR [Ee][+-]?
> %%
> [-+]?{DIGIT}+ { return tInt; }
>
> [-+]?{DIGIT}*"."{DIGIT}+{EXP}? |
> [-+]?{DIGIT}+"."{DIGIT}*{EXP}? |
> [-+]?{DIGIT}+{EXP} { return tFloat }
>
> [-+]?{DIGIT}*"."{DIGIT}+{EXPERR}? |
> [-+]?{DIGIT}+"."{DIGIT}*{EXPERR}? |
> [-+]?{DIGIT}+{EXPERR}
> . { return tError }
>
> I get:
> State #9 is non-accepting -
> associated rule line numbers:
> 7 11
> out-transitions: [ 0-9 ]
> jam-transitions: EOF [ \000-/ :-\377 ]
>
> 1 backing up (non-accepting) states.
>
> I have not been able to fix this backup. Can you get rid of the one
> backup? Is there a better way to code this?

Return to the comp.compilers page.
Search the comp.compilers archives again.