Hi, I tried this one, too, but it does not work :) But, just for your information, it is the grammar (not the parser) that fails on this one. Cheers, Doru On Mon, Dec 19, 2011 at 2:15 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
mmm... this one should work:
/top/*/second
(this is also valid in xpath, but not usually used... I'll add the wildcard as expected to next version)
El 19/12/2011, a las 10:10a.m., Tudor Girba escribió:
Thanks. It works now :)
Regarding the wildcard expression (//), is it correct to assume that it does not work for now, or is there some hidden trigger? :)
I tried this: xml := '<root> Â Â Â <top> Â Â Â Â Â Â Â <second/> Â Â Â </top> </root>'. element := PPXmlParser parse: xml. element find: '/top/second'. "--> this works fine" element find: '/top//second'. "--> this does not"
Cheers, Doru
On Mon, Dec 19, 2011 at 1:38 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
El 19/12/2011, a las 9:11a.m., Tudor Girba escribió:
Thanks, Esteban.
I gave it a try, but I cannot seem to make it work (and there are no tests :)).
yes... I know that :( I will add them when I can spare some time... and a couple of examples too :P
Here is an example of what I tried: xml := '<root> Â Â Â <topChild/> </root>'. element := PPXmlParser parse: xml. element find: 'root/topChild'
there is a "known" issue (known by me :( ): PetitXPath is ignoring "document root element"... this is a stupid error and I will fix it (real reason is that when I coded it, I assumed "first element is always unique, so... let's get rid of it"... and yes I know it was a stupid assumption... but I needed this working really fast or my client would became upset)
So... if you do:
element find: '/topChild'
It should work... good thing is other ppl using this stuff encourages me to make it work as it should be :)
cheers, Esteban
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"