Code conventions are what they are called - conventions. You dont HAVE to follow them, it's just a guideline so different developers can work together easily.
On some occasions, you can actually make some conventions break compilation... the java compiler can be set with flags determining how "bad" are different warnings. if you decide that even conventions should be errors, the project would not compile. (under eclipse you can see it in Window->Preferences->Java->Compiler->Errors/Warnings). On Sunday, December 16, 2012 8:24:44 PM UTC+2, latimerius wrote: > > On Sun, Dec 16, 2012 at 10:47 AM, Piren <gpi...@gmail.com <javascript:>>wrote: > >> >> http://www.oracle.com/technetwork/java/javase/documentation/codeconventions-135099.html#367 >> >> basically they say the naming is mixed case, so i guess the only issue is >> that you have an underscore there. >> > > I'm only asking as code conventions, however important they might be in > some contexts, are a matter of taste and circumstances and their violation > does not constitute language non-compliance in languages I'm familiar with. > > As I don't consider myself a Java expert I was just curious if they really > actually made code conventions part of the language definition. I > suspected they didn't since I notice my compiler doesn't break compilation > for a stray underscore. ;-) > > >> you should look out, the java police is out to get you :) >> > > Believe me, I'm trying. ;-) > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
