Skip to main content

Which of these Java reserved words should be unreserved

goto
34% (106 votes)
inner/outer
5% (14 votes)
generic
3% (8 votes)
cast
5% (14 votes)
rest
10% (32 votes)
Other (add comment)
2% (5 votes)
Keep all of them
42% (132 votes)
Total votes: 311

Comments

Were are these defined as reserved words?

>rather than assert in the classical rule programming sense um, i've never heard of assert being used in that context are you not thinking of assign?

This question is bad designed

I vote for "goto" at first glance, becuase I WANT "goto" statement for Java. Immediately after that, I revote "Keep All of them" since I found I'm cheated. And, after that, I realized none of them is reserved, except "goto" Stupid question

transient and volatile

transient and volatile, I kind of know what these do, never used them, get rid of them

transient and volatile

Transient is used for serialization and is VERY important. Volatile is used in multi threading. It has been and is supported on all JVM and is likewise very important. I suggest you come up to speed on the language you claim to code in.

transient and volatile

many people never have a need for coding serialisation support or fine grained multithreading code so may never encounter these keywords. Just because someone doesn't use all parts of the language doesn't mean they don't know it...

transient and volatile

I don't think there's anything fine-grained about using serialization. It's a necessity any time you want to create thread-safe objects. If you are suggesting that most people never write multithreaded code in the first place, then OK.

transient and volatile

IMO it does when they advocate getting rid of the keywords as the person I originally replied to did.

transient and volatile

I use transient a lot for selected fields in RMI data objects. Is volatile actually supported in any JVM?

transient and volatile

Yes. They are required to! Java 1.5 has a memory model revision attached to it that is going to drastically improve the use of the volatile keyword. The old one was missing guarantees when it came to the final keyword and in regards to other volatile variables. Read Doug Lea's concurrency book for more info on volatile.