From: "Weirich, James" Date: 2003-12-06T03:44:15+09:00 Subject: Protected/Private Instance Variables and Selector Namespaces ------=_NextPartTM-000-f88bb392-4dc9-4ab2-bc9b-5a29e6fb3b0f Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3BB5E.06BD7273" ------_=_NextPart_001_01C3BB5E.06BD7273 Content-Type: text/plain Here's a thought... How does the protected/private instance variable issue interact with the selector namespace issue? Would it be possible to apply the (at this time unspecified) selector namespace mechanism to the problem if making instance variables private? -- -- Jim Weirich / Compuware -- FWP Capture Services ------_=_NextPart_001_01C3BB5E.06BD7273 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Protected/Private Instance Variables and Selector = Namespaces

Here's a thought...

How does the protected/private = instance variable issue interact with the selector namespace = issue?  Would it be possible to apply the (at this time = unspecified) selector namespace mechanism to the problem if making = instance variables private? 

--
-- Jim Weirich / Compuware
-- FWP Capture Services

------_=_NextPart_001_01C3BB5E.06BD7273-- ------=_NextPartTM-000-f88bb392-4dc9-4ab2-bc9b-5a29e6fb3b0f--