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 downloading the workbench from
>>> http://my.openehr.org/wsvn/oe_distrib/windows/adl_workbench/?rev=0&sc=0
>>> - you can double check what the reference parser does).
>>
>>
>>
>>
>> Does this mean that changes will be required in the implementation of
>> the specifications ?
>>
> not sure what you mean here Rahil???
Oh I meant whether the ADLParser will be modified to be able to deal
with values demarcated with commas such as the problem I presented
initially viz. value matches {"Patient", "Relative"}. At the moment a
all to the parse( ) method on an ADL file with values stored as
comma-delimited, results in a compile-time error and all my processing
of the file ends there. If the parser can deal with comma-delimited
values my file will parse properly.
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.
Hope Ive been a bit more clear. I think Rong might want to give his
comments on this as well.
Thanks
Rahil
>
> - thomas
>
> -
> If you have any questions about using this list,
> please send a message to d.lloyd at openehr.org
>
>
--
Rahil Qamar
Ph.D. Student
Room 2.89 Kilburn Building
University of Manchester
Work number: +44 (0) 161 275 5719
Email: qamarr at cs.man.ac.uk
Website: http://www.cs.man.ac.uk/~qamarr/
-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org
