Re: [bug #4189] broken bycopy in DO

[Richard Frith-Macdonald]

On Friday, July 4, 2003, at 02:00  pm, Richard Frith-Macdonald wrote:

> On Friday, July 4, 2003, at 01:42  pm, Alexander Malmberg wrote:
> > However, there also seem to be serious problems in the handling of
> > @protocol(), and I'm not sure that can be worked around. Nicola fixed
> > those problems in gcc, so he can probably tell you more.
>
> Now that might be a real issue ... I have no idea what problems might 
> be
> with it and how to produce them though.  I'll ask Nicola.

After speaking to Nicola,  It seems that the @protocol() issue was 
causing
a crash if you used @protocol() to get and use a protocol which was not
implemented in the local compilation unit.

This *is* an issue preventing you from  using setProtocolForProxy: in 
some
sotuations in code built with an olk compiler ... which is very 
annoying as
the documentation tells you you *should* use it.

However, we don't think it's an issue for the recent DO changes, since 
these
work with objects of classes which conform to the protocols, and those 
classes
must have the protocols they conform to implemented.

So ... as far as I know the new code should work with older compilers.