Re: [gobo-eiffel-develop] Re: Re: CDATA

[Eric B. <er...@go...>]

Sven Ehrke wrote:
> 
> > Of course you cannot understand: it seems that the entities
> > that I put in my previous message have been interpreted
> > either on my side or your side by the mail tool. Here is
> > again what I wrote, in the hope that it will appear correctly
> > this time:
> >
> >    <getest config="getest.cfg"
> >      compile="geant compile_ise > xcompile.log 2>&1"/>
> 
> Sorry for my stupidity but I still cannot see the
> xml entity in the compile attribute.

Hmmm, I don't know what to say. This is not what I sent.
Although there is the same thing in the mailing list archive,
I received from the mailing list the exact message that
I sent. So let me try it again:

    <getest config="getest.cfg"
      compile="geant compile_ise &.gt.; xcompile.log 2&.gt.;.&.amp.;1"/>

Please remove the . characters, they are just here to avoid
the entity expansion.

> So with the support of entities it probably would look like this
> (I hope it comes through the mail proberly):
> 
>    <getest config="getest.cfg"
>      compile="geant compile_ise &gt; xcompile.log 2&gt;&1"/>
> 
> Maybe the ampersand has to replaced by an entity as well (I cannot
> remeber the symbol for it right now).

Yes, this is what I'm trying to say since the begining,
but somehow the entities are expanded when you receive them.
Note that even though the above is a quote from your message,
the entities may appear expanded again when you will receive
them ;-(

> But personally I find the CDATA version more readable.

OK, I'll try to implement that in the parser. BTW, is it
allowed to have CDATA in the string value of attributes
like that?

> > > If you are talking about
> > > xml entities you are right: they are not handled.
> >
> > But they should, no?
> 
> Yes, would be nice. But the current implementation does not support
> many features of a professional XML parser. But we can add missing
> features as we need them.

I understand that your Eiffel implementation of the XML parser
is a minimal implementation. I think that the long term solution
would be to replace it and integrate the full-fledge Eiffel
implementation of the XML parser developed by Franck Arnaud
instead.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com