Re: __weak definition and problems with Obj-C

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Thu, May 07, 2015 at 11:35:32AM +0100, David Brownlee wrote:
> On 7 May 2015 at 10:48, Martin Husemann <martin%duskware.de@localhost> wrote:
> >
> > On Thu, May 07, 2015 at 09:46:46AM +0200, Riccardo Mottola wrote:
> > > You can continue with your stubbornness or not, up to you. I like
> > > operating systems who play nice to different languages and NetBSD has a
> > > long tradition of being friendly.
> >
> > It also has a long tradition of using the cleanest solution, and messing
> > up our headers with #ifndef for various foreign environments sounds
> > a bit unclean to me.
> 
> Thought not having it is a show stopper for using Obj-C, and a NOP for
> anyone not defining __OBJC__.
> 
> How about adding in the logic but include a #warn to the effect that
> its a workaround for a design flaw in Obj-C :)

I'm strongly assuming that every Objective C header is going to include
some common gnustep or whatever header. As such I don't see why that
place can't undef the macro first.

Joerg