This is a typical problem, but we can always have aliases and metion that its deprecated. Also another option would be to retain existing stuff, and allow camel case for variables of user submitted programs and libraries.
Sunish On Wed, Mar 17, 2010 at 9:31 PM, Joep Suijs <[email protected]> wrote: > Hi Mike, > > > > No, no.. > > no existing API needs to change, people can use all lower case if they > > prefer > > No enforcing tool of casing needed. Maybe only insist "includes" are > > all lower case. > Let's take "serial_hw_data" for example. > > Now you know by heart how to spell this. > But what if we change the convention? > > Serial_Hw_Data? > SerialHwData? > serial_hw_data? > > Joep > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<jallib%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > -- You received this message because you are subscribed to the Google Groups "jallib" 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/jallib?hl=en.
