Comments on: Three Cheers for CakePHP Backwards Compatibility http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/ The big yellow one's the sun. Sun, 29 Aug 2010 22:32:00 -0500 http://wordpress.org/?v=2.9 hourly 1 By: britg http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/comment-page-1/#comment-302 britg Tue, 27 Jan 2009 22:01:49 +0000 http://britg.com/?p=746#comment-302 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. 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.

]]> By: mattmillr http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/comment-page-1/#comment-301 mattmillr Tue, 27 Jan 2009 21:41:28 +0000 http://britg.com/?p=746#comment-301 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.<br><br>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. 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.

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.

]]> By: britg http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/comment-page-1/#comment-210 britg Tue, 27 Jan 2009 14:01:49 +0000 http://britg.com/?p=746#comment-210 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. 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.

]]> By: mattmillr http://britg.com/2009/01/27/three-cheers-for-cakephp-backwards-compatibility/comment-page-1/#comment-209 mattmillr Tue, 27 Jan 2009 13:41:28 +0000 http://britg.com/?p=746#comment-209 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.<br><br>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. 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.

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.

]]>