<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 06 Jul 2008 16:51:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ken Guest's Blog: Validation in Depth - a retort to using just regular expressions]]></title>
      <guid>http://www.phpdeveloper.org/news/10273</guid>
      <link>http://www.phpdeveloper.org/news/10273</link>
      <description><![CDATA[<p>
<i>Ken Guest</i>, in a response to <a href="http://www.phpguru.org/article/300">another post</a> from a different blogger, has posted some of <a href="http://blogs.linux.ie/kenguest/2008/05/26/validation-in-depth-a-retort-to-using-just-regular-expressions/">his own</a> validation replacements for the regular expression method the other blogger chose.
</p>
<blockquote>
I've noticed that <a href="http://www.phpguru.org/">Richard Heyes</a>, who professes himself to be a php guru, deleted my comment on <a href="http://www.phpguru.org/article/300">his "Some common regular expressions" posting</a> which simply pointed out his expressions didn't quite do the job and suggested a few <A href="http://pear.php.net/">PEAR packages</a> that should be used instead of the expressions that he proffered
</blockquote>
<p>
His examples have the benefit of what he calls "defense in depth" - the functionality to catch a bit more than just a regular expression can alone. His examples include <a href="http://pear.php.net/package/Validate">PEAR_Validate</a> for email addresses, <a href="http://pear.php.net/package/Net_CheckIP2">Net_CheckIP2</a> for IP addresses and the <a href="http://pear.php.net/package/Validate_UK/">Validate_UK</a> package for the sort code and telephone numbers.
</p>]]></description>
      <pubDate>Tue, 27 May 2008 07:58:54 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Eirik Hoem's Blog: Handy online regex tool for PHP, Perl, JS and Python]]></title>
      <guid>http://www.phpdeveloper.org/news/10121</guid>
      <link>http://www.phpdeveloper.org/news/10121</link>
      <description><![CDATA[<p>
<i>Eirik Hoem</i> has <a href="http://blog.eirikhoem.net/index.php/2008/04/29/handy-online-regex-tool-for-php-perl-js-and-python/">pointed out</a> an online tool a coworker shared with him to work with regular expressions for multiple languages.
</p>
<blockquote>
A coworker of mine has been working on a ajax enabled regex tool which lets you evaluate regex expressions in several languages (including PHP PCRE and PHP POSIX) with instant results.
</blockquote>
<p>
<a href="http://regex.larsolavtorvik.com/">The tool</a> lets you put in the string you want to match again and the pattern you want to match with. The results are automatically populated below it, making it easy to fine-tune your expression to only what you want.
</p>]]></description>
      <pubDate>Tue, 06 May 2008 12:09:14 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Developer Tutorials Blog: Learn regular expressions in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/10085</guid>
      <link>http://www.phpdeveloper.org/news/10085</link>
      <description><![CDATA[<p>
On the Developer Tutorials blog, <i>Akash Mehta</i> <a href="http://www.developertutorials.com/blog/php/learn-regular-expressions-in-php-152/">offers some suggestions</a> of resources and methods for learning how to use regular expressions in your PHP applications.
</p>
<blockquote>
When it comes to quickly dealing with large blocks of data, batch processing operations or screen scraping, regular expressions are often the most effective solution. There's just one problem, though - learning them can be as hard as learning a new language altogether. Here's how to get off to a flying start.
</blockquote>
<p>
He points you first in the direction of the preg_* functions then towards a few examples (like with mod_rewrite) and tools to help you understand how things match, like the regex tested extension for firefox and the regular expression <a href="http://www.ilovejackdaniels.com/regular_expressions_cheat_sheet.png">cheat sheet</a> on ILoveJackDaniels.com.
</p>]]></description>
      <pubDate>Thu, 01 May 2008 08:48:05 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DotVoid.com: Parsing the user agent string using PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/7182</guid>
      <link>http://www.phpdeveloper.org/news/7182</link>
      <description><![CDATA[<p>
On the Dotvoid.com blog today, there's <a href="http://www.dotvoid.com/view.php?id=68">a new post</a> that shares some handy code to parse out information from the incoming user agent string for the visitors for your site.
</p>
<blockquote>
Recently I experimented a bit with an Apache log file analyzer written in PHP. It's not all that difficult were it not for trying to parse the browser, or user agent, string. [...] For my purposes I don't care much for the operating system details. This is the result so far. I'm still not very satisfied but I thought maybe other people might be interested and maybe help out.
</blockquote>
<p>
He <a href="http://www.dotvoid.com/view.php?id=68">provides the code</a> in the format of an encapsulated PHP function that returns the product they're using, the version number of the browser and other various comments.
</p>]]></description>
      <pubDate>Mon, 29 Jan 2007 15:11:57 -0600</pubDate>
    </item>
  </channel>
</rss>
