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 need a mutable boolean field in Java (I will return this field via get* method later and it should be possible to modify this field).
Boolean doesn’t work because there are no set* methods in the Boolean class (I would say that Boolean is immutable, you can only change the reference, but you can’t change the object itself).
I guess I can use Boolean array of size 1. But probably there are more elegant solutions?
Why doesn’t Java have such a simple thing?
Immutable classes are easier to work with. They’ll never change and there will be no problems with concurrent code. (Basically, there are fewer possibilities to break them.)
If you would like to return a reference to your Boolean value, you can use
java.util.concurrent.atomic.AtomicBooleanif you’re working with multiple threads or plain oldorg.apache.commons.lang.mutable.MutableBoolean.