From 55af56f96072ce11e99718d393f0f46c63948d3d Mon Sep 17 00:00:00 2001 From: Mark Pilgrim Date: Sat, 18 Apr 2009 11:38:56 -0400 Subject: [PATCH] one more typo [h/t G.P.] --- regular-expressions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/regular-expressions.html b/regular-expressions.html index 7d17a18..8b56fe0 100644 --- a/regular-expressions.html +++ b/regular-expressions.html @@ -375,7 +375,7 @@ body{counter-reset:h1 4}
  1. Note the lack of ^ in this regular expression. You are not matching the beginning of the string anymore. There’s nothing that says you need to match the entire input with your regular expression. The regular expression engine will do the hard work of figuring out where the input string starts to match, and go from there.
  2. Now you can successfully parse a phone number that includes leading characters and a leading digit, plus any number of any kind of separators around each part of the phone number. -
  3. Sanity check. this still works. +
  4. Sanity check. This still works.
  5. That still works too.

See how quickly a regular expression can get out of control? Take a quick glance at any of the previous iterations. Can you tell the difference between one and the next?