Regular Expressions allow you to check if a string of text matches a particular pattern - for example to see if the data that a user has entered into a form looks like a Postcode / zipcode ... and then to extract the vital parts of the string that you're checking into separate variables.

Down the left here, I've written the regular expression to match a British Postcode - this involves describing what a postcode looks like in great detail.

Here are some of the elements:
^ - Starts with
[A-Z] - Capital Letter
[0-9] - Digit
+ - one or more of the previous item
? - previous item is optional
{2} - exactly 2 of the previous item
$ - ends with

The round brackets are known as "capture parentheses" - or in easy English, they're used to indicate which parts of the pattern match against interesting bits of the incoming string that you would like to capture into separate variables when you match.



There are complete books on regular expressions, but this summary to the right shows you the basic types of elements ...

Anchors or "zero width assersions" indicate thinsg like "starts with" and "ends with" so you can match at the beginning, in the middle, at the end of, or a whole string.

Literals match a single character (perhaps modified by a following count) exactly.

Character groups match any one character from a whole group of possibilities (perhaps modified by a following count) exactly.

Counts say how many times the previous element may occur - the default is once.

You can also use (...) to group elements for capture, | which means "or" (a.k.a. alternation) and a few other types.


There are two regular expression engines in PHP - there's the ereg series which are based on POSIX regular expressions, and the preg series which are based on the Perl standard. In easy terms, the preg flavour are shorter to write and more efficient in operation, but harder to understand and maintain.

One of the big questions with Regular Expressions is "are they case sensitive?" By default, yes they are, but you can add an "i" to ignore case - in different places in the syntax depending on if you're using ereg or preg.


If you're matching and capturing, you need to be very careful just which parts of the regular expression engine match which parts of the incoming string, as there can be many alternatives. You should remember that matching always starts as far to the left as it can, and that counts such as "+" always match as MANY characters as possible. If you use counts such as "+?" instead, then you're doing what is called a "sparse" rather than a "greedy" match, and that will match as few characters as possible.

The diagram shows the effect of sparse v greedy on a match to an email address with two @ characters in it. Most of the time, it'll be greedy you want to use ... sparse is useful especially when you're identifying / stripping HTML tags, though.


The boards / notes above come from the PHP Techniques Workshop that I was presenting yesterday ... it's a regular public course and we would welcome YOU on it ;-)
(written 2008-09-16 07:52:55)

 H107 - String Handling in PHP
  [2238] Handling nasty characters - Perl, PHP, Python, Tcl, Lua - (2009-06-14)
  [2165] Making Regular Expressions easy to read and maintain - (2009-05-10)
  [2046] Finding variations on a surname - (2009-02-17)
  [1613] Regular expression for 6 digits OR 25 digits - (2008-04-16)
  [1603] Do not SHOUT and do not whisper - (2008-04-06)
  [1533] Short and sweet and sticky - PHP form input - (2008-02-06)
  [1372] A taster PHP expression ... - (2007-09-30)
  [1336] Ignore case in Regular Expression - (2007-09-08)
  [1195] Regular Express Primer - (2007-05-20)
  [1058] PHP Regular expression to extrtact link and text - (2007-01-31)
  [1008] Date conversion - PHP - (2006-12-26)
  [728] Looking ahead and behind in a Regular Expression - (2006-05-22)
  [716] Evaluating arithmetic expressions in configuration files - (2006-05-10)
  [642] How similar are two words - (2006-03-11)
  [608] Don't expose your regular expressions - (2006-02-15)
  [589] Robust PHP user inputs - (2006-02-03)
  [574] PHP - dividing a string up into pieces - (2006-01-23)
  [560] The fencepost problem - (2006-01-10)
  [558] Converting between acres and hectares - (2006-01-08)
  [493] Running a Perl script within a PHP page - (2005-11-12)
  [463] Splitting the difference - (2005-10-13)
  [422] PHP Magic Quotes - (2005-08-22)
  [337] the array returned by preg_match_all - (2005-06-06)
  [54] PHP and natural sorting - (2004-09-19)
  [31] Here documents - (2004-08-28)

Q802 - Object Orientation and General technical topics - Regular Expression Elements
  [1849] String matching in Perl with Regular Expressions - (2008-10-20)
  [1766] Diagrams to show you how - Tomcat, Java, PHP - (2008-08-22)
  [1480] Next course - 7th January 2008, Regular Expressions - (2007-12-21)
  [453] Commenting Perl regular expressions - (2005-09-30)

Back to What does an browser understand? What does an HTML document contain?

Previous and next or Horse's mouth home

Forward to Spiders Web

FTP passive mode - a sometimes cure for upload hangs
Motorcycles welcome at Well House Manor
Will your backups work if you have to restore them?
Spiders Web
Regular Expressions in PHP
What does an browser understand? What does an HTML document contain?
I have been working hard but I do not expect you noticed
libwww-perl and Indy Library in your server logs?
What have iTime, honeytrapagency and domain listing center got in common?
Refactoring - a PHP demo becomes a production page