[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Alternative algorithm to restrict use of data/string in patterns.
Kohsuke KAWAGUCHI wrote: > Also, as you pointed out, interleave has to be modified to: > > case: p == <interleave> p1 p2 </interleave> > check( p1, fpds ) > check( p2, fpds ) > if( p1 contains <data/> or <string/>, > && p2 contains <data/>,<string/>,<anyString/> or <element/>, > or viceversa) > this pattern is illegal! This will report that the next pattern is illegal, but it does not have to be disallowed. <interleave> <group><notAllowed><string>foo</string></group> <group><notAllowed><string>foo</string></group> </inteleave> Cheers, Makoto
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC