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.
On application startup, I am instantiating a class on a background thread, then assigning it to a variable. I later access that variable from my main thread. This variable is only assigned once.
My understanding is that I don’t need to use the volatile keyword here, because the reference could not be cached until it is first accessed in the UI thread. Am I correct in my thinking, or am I missing something?
Yes. Caching is only an issue when one thread repeatedly reads a variable (written to from another thread).
And because assigning to a reference is atomic you’re safe.