parsing error

Rahil wrote: > Hi Rong > > Rong Chen wrote: > >> There is some mismatch between the test description of String >> constraint and the syntax specification in the ADL spec document. >> >> Since the Java parser is mostly based on the syntax specification, the >> support for string list within c_st

parsing error

Rahil wrote: > > Thats great. I had a look at the subversion repository. Where can I > download the latest adl-parser jar file from? I had downloaded the > earlier version from > http://www.acode.se/frameset.jsp?cat=4&subcat=2&lang=en but cant see > the latest version up there. Also, have chan

parsing error

Hi Rong Rong Chen wrote: > There is some mismatch between the test description of String > constraint and the syntax specification in the ADL spec document. > > Since the Java parser is mostly based on the syntax specification, the > support for string list within c_string is already there; but

parsing error

> Rong mentioned something about the ADL specification, which is why I > wanted to know if the parser functionality might have to be changed so > that such an error does not occur. There is some mismatch between the test description of String constraint and the syntax specification in the ADL s

parsing error

Hi Tom Thomas Beale wrote: > Rahil wrote: > >> Hi Tom >> >>> to help, see the attached archetype - it includes all the parsable >>> constraints for basic types. Both {"list", "of", "strings"} and >>> {/list|of|strings|/} are supported in ADL and in the reference >>> parser (trying downloa

parsing error

Rahil wrote: > Hi Tom > >>> >> to help, see the attached archetype - it includes all the parsable >> constraints for basic types. Both {"list", "of", "strings"} and >> {/list|of|strings|/} are supported in ADL and in the reference parser >> (trying downloading the workbench from >> http://my.o

parsing error

Hi Tom Thomas Beale wrote: > Sam Heard wrote: > >> Dear Rahil >> >> The syntax for allowable text string values in the .Net parser and >> Tom's I believe is a set of delimited strings as you have described. >> There is no use of regular expressions here at the moment. I am not >> sure of the l

parsing error

An HTML attachment was scrubbed... URL:

parsing error

Sam Heard wrote: > Dear Rahil > > The syntax for allowable text string values in the .Net parser and > Tom's I believe is a set of delimited strings as you have described. > There is no use of regular expressions here at the moment. I am not > sure of the latest developments in the parser but t

parsing error

Rahil wrote: > Hi Sam (and Rong) > > Sam Heard wrote: > >> Dear Rahil >> >> The syntax for allowable text string values in the .Net parser and >> Tom's I believe is a set of delimited strings as you have described. >> There is no use of regular expressions here at the moment. I am not >> sure

parsing error

Hi Sam (and Rong) Sam Heard wrote: > Dear Rahil > > The syntax for allowable text string values in the .Net parser and > Tom's I believe is a set of delimited strings as you have described. > There is no use of regular expressions here at the moment. I am not > sure of the latest developments

parsing error

Hi Comments in line. Rong Chen wrote: > Rahil wrote: > >> Hi >> >> I am trying to parse an ADL file using the ADLParser API. However, >> the ADLParser is throwing up an error in the ADL file that Im passing >> it. The block of code where the error occurs is : >> >> >> ELEMENT[at00

parsing error

Rahil wrote: > Hi > > I am trying to parse an ADL file using the ADLParser API. However, the > ADLParser is throwing up an error in the ADL file that Im passing it. > The block of code where the error occurs is : > > > ELEMENT[at0008] occurrences matches {0..1} matches {-- Pers

parsing error

Hi I am trying to parse an ADL file using the ADLParser API. However, the ADLParser is throwing up an error in the ADL file that Im passing it. The block of code where the error occurs is : ELEMENT[at0008] occurrences matches {0..1} matches {-- Person val