Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would like your opinion about using Upper or lowerCamelCase in a case insensitive and procedural language (Oracle PL/SQL).
Some guys wanna use this pattern in my job, but the programmers don’t like the idea…
Oracle Forms and Reports do not support autocomplete.
My opinion: I don’t see any reason to use Camel Case in a case insensitive language…
What’s your opinion?
CamelCase really increases readability for variables when you need multi-word names, and its easier to write than using underscores for spaces, especially for programmers who use them all the time in most common languages.
in the long run, being case insensitive should free people to use whatever case they prefer, so not sure why this is an issue, but I vote Yes for CamelCase. SQL Keywords should probably be all caps or all lower, depending on your shop standard.