string.find matching error

[rvirding]

string.find matching error

[rvirding]

It was a bug in parsing character sets in patterns. It has been fixed in commit 3d22db5.

[loucash]

This looks good, thank you.
I saw yet another difference:
lua:

> print(string.find('<a><b>1</b><c a="1">2</c></a>', '^([^<]*)<(%/?)([^>]-)(%/?)>', 4))
4   6    b

luerl:

> luerl:do("print(string.find(\"<a><b>1</b><c a=\\\"1\\\">2</c></a>\",\"^([^<]*)<(%/?)([^>]-)(%/?)>\", 4))").
nil

[rvirding]

It was a bug in how the beginning of string anchor '^' was handled when not starting at the beginning of the string. It now follows Lua. It has been fixed in commit 5c1feb7.

[loucash]

I still experience those differences:

> print(string.find("<a>1</a>", "^([^<]*)<(%/?)([^>]-)(%/?)>", 4))
4   8   1   /   a

> luerl:do("print(string.find(\"<a>1</a>\",\"^([^<]*)<(%/?)([^>]-)(%/?)>\", 4))").
4 8 < a >

[rvirding]

You haven't heard the adage: I had a problem so I used regular expressions, now I have two problems. I will check but I am guessing I just counted wrong as the chars are one position off.

[loucash]

Ha! I hope i will soon get to know this part good enough to send not only bug reports, but also patches ;-)

[rvirding]

I was counting the offsets incorrectly. It now works on all your 3 test cases so far. It has been fixed in commit 63833f8.

If you have any cases to test for string.match, string.gsub and string.format please run them as well.

[loucash]

That worked! Here is my little side project as POC of how someone can use luerl, xml parser: https://github.com/loucash/luerlxml