Re: Some (minor) issues arising from testing a new IXML implementation

> Tests assume execution on a Unix machine

That’s an oversight.

> Several of the tests have grammars that orient on a line-based
> structure and as such use -#a or ~[.... #a] terminals to (not)match a
> line ending. Unfortunately of course running on a Windows machine a
[…]

Yes, definitely. If you feel like making the changes and filing a PR for
the test suite, I’ll be happy to test the PR against my non-Windows
machine.

Alternatively, I’ll try to fix the tests as soon as I can.

> Comment retention within promiscuous use of whitespace
[…]
> and some additional comments added to the input rule:
>
>  a {1} : {2} ^ {3} "b" {4} .
>
> which might parse as:
>
>  <rule name="a">
>     <comment>1</comment>
>     <comment>2</comment>   
>     <literal tmark="^" string="b">
>         <comment>4</comment>
>     </literal>
> </rule>
>
> but where should comment 3 be stored?

If there was more time, I’d suggest that we review the grammar and make
more delicate choices about where comments are allowed to go. But we
don’t have more time, so I think we should just live with it for version
1.0. We don’t have a requirement to round trip losslessly, so I think
implementors are free to do their best.

> The test ixml/ixml-one-line needs whitespace after most of the
> rule-concluding periods, to meet the current spec.

I thought I’d fixed that. I wonder if I have an un-pushed commit. Will
check when I have a chance. A bit busy just at the moment :-)

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica