RE: gnubol: problem 2.

["William M. Klein" <wmklein@ix.netcom.com>]

I wish I really understood this "stuff" - but does

>
> /*
>   in this rule specific, explicated continuations
>   provide a basis for disambiguation; the natural tendency
>   would be to reference sub rules that have optional /* empty */
>   alternates. That is the key: epsilons would compete in the 'continue'
>   position, leading to r/r or s/r
> */
> ref_data :
>    ref_data_simple_or_qual
>    { /* simple */ ;}
>  | ref_data_simple_or_qual PAR_OPEN ref_data PAR_CLOSE
>    { /* subscripted */ ;}
>  | ref_data_simple_or_qual PAR_OPEN ref_data COLON ref_data PAR_CLOSE
>    { /* fully ref modified     */ ;}
>  | ref_data_simple_or_qual PAR_OPEN ref_data COLON PAR_CLOSE
>    { /* partially ref modified */ ;}
> ;
>
   ... etc

Handle reference modification using arithmetic expression, e.g.

    data-name (data-name2 + 2:) *> reference modification
        versus
    data-name (data-name2 +2) *> two subscripts
        versus
    data-name (index-name + 2) * relative indexing

it may be in those rules, but I didn't see it there (in a form that I could
pick up)



--
This message was sent through the gnu-cobol mailing list.  To remove yourself
from this mailing list, send a message to majordomo@lusars.net with the
words "unsubscribe gnu-cobol" in the message body.  For more information on
the GNU COBOL project, send mail to gnu-cobol-owner@lusars.net.