Why do we check value_flag after read method?

Related to cppTango#1407 (closed)

During discussion of this issue in cppTango meeting, I was asked with a question, which I could not really answer:

Why do we check value_flag after read method? Would it be better to force value to be set if the method returns something?

I see only one explanation: with the current implementation, setting value for the second time will result in a memory leak...

Assignee Loading
Time tracking Loading