Comments on: WordPress & PHP 5 http://robinadr.com/2007/07/wordpress_php_5 Wed, 18 Aug 2010 06:30:29 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: mohanraj.s http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-2556 mohanraj.s Mon, 29 Jun 2009 05:53:16 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-2556 <p>d</p> d

]]> By: Blog Roundup for the 23rd of July 2007 :: Christopher Ross http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-2276 Blog Roundup for the 23rd of July 2007 :: Christopher Ross Mon, 27 Oct 2008 01:56:16 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-2276 <p>[...] like the digg it one Take a look at What Makes a WordPress Theme Great?. It was marvelous to read wordpress & php 5. It was sound to get a lot from wordpress plugin competition updates. Advice for web 1.0 to 2.0 [...]</p> […] like the digg it one Take a look at What Makes a WordPress Theme Great?. It was marvelous to read wordpress & php 5. It was sound to get a lot from wordpress plugin competition updates. Advice for web 1.0 to 2.0 […]

]]> By: Matt http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-17 Matt Tue, 24 Jul 2007 08:35:14 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-17 <p>It's a neat feature, but the places we output XML are either in the XML-RPC server, which has proven quite robust already, or in the RSS/etc templates, which are pretty simple and in line with every other template in WP. If we moved to full serialization for RSS our actions and hooks would have to change as well.</p> It’s a neat feature, but the places we output XML are either in the XML-RPC server, which has proven quite robust already, or in the RSS/etc templates, which are pretty simple and in line with every other template in WP. If we moved to full serialization for RSS our actions and hooks would have to change as well.

]]> By: Robin http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-16 Robin Tue, 24 Jul 2007 07:41:31 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-16 <p>True, but how about true XML serialization?</p> True, but how about true XML serialization?

]]> By: Matt http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-15 Matt Tue, 24 Jul 2007 03:03:50 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-15 <p>It's different, but I don't see that any better or worse. We'd need to keep the old function wrappers around anyway for compatibility, so overall we'd just increase the weight of WP.</p> It’s different, but I don’t see that any better or worse. We’d need to keep the old function wrappers around anyway for compatibility, so overall we’d just increase the weight of WP.

]]> By: Robin http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-14 Robin Mon, 23 Jul 2007 23:24:32 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-14 <p>Also, did you read the funkatron.com post? Global variables are, IMO, a clumsy and error-prone way of handling what could be done with namespaces.</p> Also, did you read the funkatron.com post? Global variables are, IMO, a clumsy and error-prone way of handling what could be done with namespaces.

]]> By: Robin http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-13 Robin Mon, 23 Jul 2007 23:18:28 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-13 <p>One thing we could do better with PHP 5's OOP is the options handling. Using <a href="http://it.php.net/manual/en/language.oop5.overloading.php" rel="nofollow">method overloading</a> we could create a much easier way to add, set and remove variables. So instead of add_option, update_option and et cetera, you could merely refer to Options::html_type and manipulate that with unset() and so on.</p> <p>Also, that would make caching more transparent and IMO it's a lot easier to handle options that way.</p> One thing we could do better with PHP 5’s OOP is the options handling. Using method overloading we could create a much easier way to add, set and remove variables. So instead of add_option, update_option and et cetera, you could merely refer to Options::html_type and manipulate that with unset() and so on.

Also, that would make caching more transparent and IMO it’s a lot easier to handle options that way.

]]> By: johnbillion http://robinadr.com/2007/07/wordpress_php_5/comment-page-1#comment-12 johnbillion Mon, 23 Jul 2007 22:01:29 +0000 http://robinadr.com/2007/07/wordpress_php_5#comment-12 <p>Matt, then tell us why you strongly disagree!</p> Matt, then tell us why you strongly disagree!

]]>