<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Oops… typo...<br class=""><div><blockquote type="cite" class=""><div class="">On Dec 20, 2016, at 12:29 PM, David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""></div></div></blockquote><blockquote type="cite" class=""><br class=""></blockquote><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">[...] According to “Daveo” (not me) on stackoverflow (<a href="http://stackoverflow.com/questions/3809401/what-is-a-good-regular-expression-to-match-a-url" class="">http://stackoverflow.com/questions/3809401/what-is-a-good-regular-expression-to-match-a-url</a>), the regex for the regex for an URL is: […]</div></div></div></blockquote>That “for the regex” in the middle of the text after the link shouldn’t be there… The regex I posted supposedly matches URLs, not strings which would themselves form a regex that would match URLs.</div><div><br class=""></div><div>hehe… nested regexing… that’s gotta be useful for something… lol</div><div><br class=""></div><div>- Dave Sweeris</div></body></html>