Anyone have any books that would help on learning how to "refine" code to make it more acceptable and professional looking and the correct way to do things in Java. Not quite a how to book, just more of de facto standards of how to do things.
Writing "proper" Java
- Thread starter AFB
- Start date
Nice. That's cool actually, my prof for Intro to Java 1 & 2 sort of makes you code to the same rules as that page describes.
Yeah my "Intermediate Java" professor makes us follow all conventions for labs or it's points off, and we must have javadoc compatible comments.
kamper
Diamond Member
- Mar 18, 2003
- 5,513
- 0
- 0
Holy freakin' old guide! They stated that they use make to build 
I agree with most of it but here are my few beefs:
-4 spaces to indent is too much. 3 is a very common standard but I've got nothing against 2.
-80 character lines is too small (I think 100 is a reasonable goal). Multiline statements are extremely difficult to read so this point and the last should be tailored towards keeping things on one line
-a loop with no body should absolutely not be termintated with a semi-colon (chapter 7). No one will see the semi-colon and they are bound to assume that the next statement is actually part of the loop. This is just begging for infinite loops and other oddities. Loops with no body should have a {} after the clause.
-you should never use one letter variable names (not a strict rule, but I strongly prefer it that way) (chapter 8, "throwaway" variables)
I'd like to see them update this for generics and enums. Enums in particular, I've found, can get a little messy if you're doing more than just enumerating (like adding methods and properties).
I agree with most of it but here are my few beefs:
-4 spaces to indent is too much. 3 is a very common standard but I've got nothing against 2.
-80 character lines is too small (I think 100 is a reasonable goal). Multiline statements are extremely difficult to read so this point and the last should be tailored towards keeping things on one line
-a loop with no body should absolutely not be termintated with a semi-colon (chapter 7). No one will see the semi-colon and they are bound to assume that the next statement is actually part of the loop. This is just begging for infinite loops and other oddities. Loops with no body should have a {} after the clause.
-you should never use one letter variable names (not a strict rule, but I strongly prefer it that way) (chapter 8, "throwaway" variables)
I'd like to see them update this for generics and enums. Enums in particular, I've found, can get a little messy if you're doing more than just enumerating (like adding methods and properties).
kamper
Diamond Member
- Mar 18, 2003
- 5,513
- 0
- 0
Not faulting the guide (or you) because it's old
Syntactically, java hasn't changed much (with the exception of 1.5) so the rules set out are still very relevant. I was just surprised to hear the words "make" and "java" and "build" all in the same sentence
kamper
Diamond Member
- Mar 18, 2003
- 5,513
- 0
- 0
I like elses on the same line as the closing brace. It keeps things compact and reminds you that the else belongs with that if statement. Technically you're starting a new block, but logically you're not. The only time I find that gets messy is if you want to document the else case (or any else ifs). You can't very well put comments above the block, as is normal for most blocks.
In general I use:
if()
{
content
}
else
{
}
this is offcourse very lengthy, but imho makes it very easy to see which brackets belong together, I also do this for anonymous inner classes:
if()
{
content
}
else
{
}
this is offcourse very lengthy, but imho makes it very easy to see which brackets belong together, I also do this for anonymous inner classes:
MartyMcFly3
Lifer
If I were to code that from what I've learned it'd be more like this. To me it just seems more organized:
I prefer English myself, but this is a school project, code had to be dutch (for most part, you dont see me translating if structures )
)nah, btn is short for button, we get tought to use general prefixes for gui elements, btn, lbl, txa, txf, etc.
SluitVenster is CloseWindow yes.
SluitVenster is CloseWindow yes.
kamper
Diamond Member
- Mar 18, 2003
- 5,513
- 0
- 0
I don't think it's that all programming languages were invented by english speakers. I think it's that they knew for the language to have a chance it would have to be accessible to english speaking people
The guy who invented python is Dutch (yay for Holland!)
<-- Dutch Canadian...
The guy who invented python is Dutch (yay for Holland!)
<-- Dutch Canadian...
i always do
if (condition) {
code
}
else {
code
}
the only time i do what's described in the page is the :
try {
code
} catch (....) {
code
}
i guess that makes it a bit inconsistent
other than that i always put an open bracket next to a function/condition
if (condition) {
code
}
else {
code
}
the only time i do what's described in the page is the :
try {
code
} catch (....) {
code
}
i guess that makes it a bit inconsistent
other than that i always put an open bracket next to a function/condition
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 22K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
Facebook
Twitter