Re: [bug #4189] broken bycopy in DO

[Nicola Pero]

> >> This *is* an issue preventing you from  using setProtocolForProxy: in some
> >> sotuations in code built with an olk compiler [snip]
> >
> > NSDistributedNotificationCenter is such a situation. I've attached a
> > patch that works around it. Not pretty, but things seem to work now
> > (better, at least; there are a couple of "Changed type signature"
> > warnings, and a few slightly odd details).
> 
> Yes, for the moment I've just disabled the use of setProtocolForProxy:
> where it might be a problem ... Probably we should use this sort of
> dummy class solution though, I'm not sure how long we will want to
> support older compilers, but if it's for a significant length of time I think
> the workaround is worth putting in.

<jumping in without really having had time to read the whole thread, so I
hope I'm not off topic>

Are we talking about the fact that using @protocol(XXX) does not work if
no class implementing the protocol XXX is compiled in the same module ?

If so, yes I think it's absolutely worth putting in a hack via a dummy
class implementing the protocol, because any compiler I know of, from
2.95.x to 3.2.x (and possibly older ones as well) suffers from this
problem.

It's going to take years before everyone has upgraded to 3.3.