On Tuesday, May 08, 2018 16:18:40 Jesse Phillips via Digitalmars-d-learn
wrote:
> On Monday, 7 May 2018 at 22:24:25 UTC, Jonathan M Davis wrote:
> > I've been considering adding more configuration options where
> > you say something like you don't care if any invalid characters
> > are encountered
On Monday, 7 May 2018 at 22:24:25 UTC, Jonathan M Davis wrote:
I've been considering adding more configuration options where
you say something like you don't care if any invalid characters
are encountered, in which case, you could cleanly parse past
something like an unescaped &, but you'd the
On Monday, May 07, 2018 22:16:58 Jesse Phillips via Digitalmars-d-learn
wrote:
> On Monday, 7 May 2018 at 19:46:00 UTC, Jesse Phillips wrote:
> > So I have an XML like document which fails to adhere completely
> > to XML. One of these such events is that & is used without
> > escaping.
> >
> > My
On Monday, May 07, 2018 19:46:00 Jesse Phillips via Digitalmars-d-learn
wrote:
> So I have an XML like document which fails to adhere completely
> to XML. One of these such events is that & is used without
> escaping.
>
> My observation is that after the exception it is possible to move
> to the n
On Monday, 7 May 2018 at 19:46:00 UTC, Jesse Phillips wrote:
So I have an XML like document which fails to adhere completely
to XML. One of these such events is that & is used without
escaping.
My observation is that after the exception it is possible to
move to the next element without issue
So I have an XML like document which fails to adhere completely
to XML. One of these such events is that & is used without
escaping.
My observation is that after the exception it is possible to move
to the next element without issue. Is this something expected and
will be maintained?
t
