On 19.01.2011, at 12:21, Bernhard Schussek wrote: > Hi everyone, > > I would like to propose changing options from underscored to camelcase > syntax (except for CLI commands, where they are naturally hyphenated). > > e.g. > date_format -> dateFormat > etc. > > I see two benefits in this change: > > 1) Less confusion about which naming convention is to apply where. I > still see developers accidentally using camel-case for options from > time to time. > > 2) The change allows a different implementation, where options are > directly written into properties of an object instead of being stored > in an associative array > > What do you think?
Well the problem is that we also set options via yaml and xml. Then again there we use - an _, which already means we need to normalize names and right now its horrible. All over the extensions we have if() statements that rekey arrays. There should be a way to easily normalize this stuff. regards Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
