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.
A co-worker asked me to change a signature from using a primitive “boolean” to using a classed “Boolean”. He didn’t offer a very good explanation why?
Have any of you heard of this and can any of you explain why it matters or doesn’t matter?
Edit: He mentioned that it was good practice for public methods.
The use of the field is just a flag that tells me whether to call one flow or another depending on whether it’s true or false.
Actually I tend to err on the side of passing small-b boolean instead, because I know that a primitive boolean is never going to be null. I’m sure there are valid reasons for using the Boolean type, but I’d want to think about its use in each case.