<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>britg - Latest Comments in Three Cheers for CakePHP Backwards Compatibility</title><link>http://britg.disqus.com/</link><description></description><atom:link href="https://britg.disqus.com/three_cheers_for_cakephp_backwards_compatibility/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 27 Jan 2009 12:01:49 -0000</lastBuildDate><item><title>Re: Three Cheers for CakePHP Backwards Compatibility</title><link>http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/#comment-5583502</link><description>&lt;p&gt;Yeah, I agree about ActionScript camel casing.  Some languages just _feel_ like they should be camelcased and other _feel_ like they are underscored -- usually correlated to whether they are OO or not.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">britg</dc:creator><pubDate>Tue, 27 Jan 2009 12:01:49 -0000</pubDate></item><item><title>Re: Three Cheers for CakePHP Backwards Compatibility</title><link>http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/#comment-5579569</link><description>&lt;p&gt;Neat. Looks like they *just don't care* whether you use underscore_separation or CamelCase to access properties. I've been mulling something like this over in the back of my mind for our own ORM layer, where we have database tables with underscores but would like to automagically expose them in ActionScript objects where the underscores would just be ugly.&lt;/p&gt;&lt;p&gt;IIRC, Flex styles do something similar depending on whether you access them as class properties or through CSS. The difference is that it matters that you use the right format in the right place.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Miller</dc:creator><pubDate>Tue, 27 Jan 2009 11:41:28 -0000</pubDate></item></channel></rss>