I found that setReadOnly() method of the CList class is protected. I wonder if it is a bug, or it was done intentionally to prevent accidental chage of ReadOnly status of the list after it has been instantiated with given R/O flag?
What do you think?
Same thing is with CMap class. I don’t believe in multiple bugs of the same type 
Must be intentional, for protection purposes. After all if I want to have this method public, I can create my own class extending the mentioned one, with setReadOnly method made public…
It’s by design and is there to make it possible to set it to read only if you’re overriding the class.