lpeg, branch v1.1.0 A mirror of https://github.com/roberto-ieru/LPeg.git https://git.lua4.win/lpeg/atom?h=v1.1.0 2023-06-26T16:29:19+00:00 Removed protocol ('http') from links in documentation 2023-06-26T16:29:19+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-26T16:29:19+00:00 urn:sha1:73a96935337d78d0e1015d7ccce6cf7470c192c4 Missing files in 'pack' script 2023-06-23T18:27:23+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-23T18:27:23+00:00 urn:sha1:e58f9bb289b1aa5cd4c96c26cccd0f69461e8436 Added a README file 2023-06-23T18:04:04+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-23T18:04:04+00:00 urn:sha1:097bebd29949edf6ed7bd55d8fb21c477ac85236 Copyright notice in module 're' 2023-06-23T17:56:42+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-23T17:56:42+00:00 urn:sha1:664da61c079f762d835ea6f875cdf3da96982bab Fold capture deprecated 2023-06-23T17:55:48+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-23T17:55:48+00:00 urn:sha1:8bc00db24975f52b52e6ef8184c216ce2feae9fd Improved documentation for accumulator captures 2023-06-22T13:51:31+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-22T13:51:31+00:00 urn:sha1:7d43b367e7a89369c1302124677a305aa0d070c7 Accumulator pattern added to the 're' module 2023-06-22T13:50:15+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-22T13:50:15+00:00 urn:sha1:4eb4419163dd6c97665b9481e9581ff32496b392 Detail in 're.lua' 2023-06-19T14:39:44+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-19T14:39:44+00:00 urn:sha1:e3f612f58dc0201beb3a86e1a5d8df9cd9158698 Distinction between 'm' and 'mm'. Some fixes in vibibility check for back captures 2023-06-19T14:14:02+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-19T14:14:02+00:00 urn:sha1:9a9ee3d9ab8ce435d743d293ec43075151370200 Full captures can contain nested captures 2023-06-15T14:28:33+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-06-15T14:28:33+00:00 urn:sha1:a561630f17e61548193666abf9a8b20f20462558 Nested captures can be recognized because they start (and end) inside the character range of the full capture. This optimization can remove a lot of 'close' captures from the capture logs.