| commit | 452600404a715b6b3540571a97cb25f443a84b8d | |
| author | Evan Schoenberg <evan@adiumx.com> | |
| Thu, 10 Jan 2008 22:47:10 +0000 (10 22:47 +0000) | ||
| committer | Evan Schoenberg <evan@adiumx.com> | |
| Thu, 10 Jan 2008 22:47:10 +0000 (10 22:47 +0000) | ||
| tree | 19c801960435af87ba6d76ca77fe4d0fed978c6d | treesnapshot (tar.gz zip) |
| parent | 08cb025092a8d7e04ced03e22d60e9a90a1e2113 | commitdiff |
I don't understand why the valid regex expression
`([0-9]{1,3}\.){3}[0-9]{1,3}`
is acting identically to
`([0-9]{1,3}\.){3}[0-9]`
in lex. It works fine for me in other tools, such as SubEthaEdit's Find dialogue.
`([0-9]{1,3}\.){3}[0-9][0-9]?[0-9]?` behaves as expected, allowing a dotted quad of 3 digits per section.
Fixes #7839
git-svn-id: svn://svn.adiumx.com/adium/trunk@22243 1c916fce-81e2-0310-a464-8ca513f45935
`([0-9]{1,3}\.){3}[0-9]{1,3}`
is acting identically to
`([0-9]{1,3}\.){3}[0-9]`
in lex. It works fine for me in other tools, such as SubEthaEdit's Find dialogue.
`([0-9]{1,3}\.){3}[0-9][0-9]?[0-9]?` behaves as expected, allowing a dotted quad of 3 digits per section.
Fixes #7839
git-svn-id: svn://svn.adiumx.com/adium/trunk@22243 1c916fce-81e2-0310-a464-8ca513f45935
| Frameworks/AIHyperlinks Framework/Source/SHLinkLexer.l | diffblobblamehistory |