Thanks for your insights guys...
I think the separate header for the mutating methods in a category should be
enough in this case.
--Graham
On 16/12/2012, at 8:28 AM, Jens Alfke j...@mooseyard.com wrote:
On Dec 14, 2012, at 3:25 PM, Graham Cox graham@bigpond.com wrote:
I have an
On Dec 14, 2012, at 3:25 PM, Graham Cox graham@bigpond.com wrote:
I have an abstract base class A and a mutable subclass AM. The class A owns a
list of subsidiary objects but only the class AM has the methods for adding
and removing these , which is what 'mutable' means for this class.
Hi all,
I'm having trouble getting this to work how I think it should, i must be
missing something.
I have an abstract base class A and a mutable subclass AM. The class A owns a
list of subsidiary objects but only the class AM has the methods for adding and
removing these , which is what
On Dec 14, 2012, at 15:25 , Graham Cox graham@bigpond.com wrote:
I have an abstract base class A and a mutable subclass AM. The class A owns a
list of subsidiary objects but only the class AM has the methods for adding
and removing these , which is what 'mutable' means for this class.
