Re: libobjc2 fails to build with gcc 5.4.0

[David Chisnall]

On 3 Apr 2017, at 19:19, Niels Grewe <address@hidden> wrote:
> 
> As I said in the pull request, I don't have any interest in GCC as an 
> Objective-C compiler anymore (hell, I haven't compiled a single line of 
> Objective-C code using gcc this year…). But I think outright dropping GCC 
> support is a bit harsh. You'd be turning up the heat a lot on existing users 
> of libobjc2 in gcc-based environments [0]. It would also be a half-baked 
> measure without removal of the legacy runtime API (objc_msg_lookup() and 
> friends). My favoured approach would be deprecation of the old runtime API 
> (and GCC support) in the next release, and removal in the release after that.

There’s big a difference between deprecating building the runtime with gcc and 
deprecating compiling other Objective-C code compiled with GCC and using the 
runtime.  I’m in no hurry to do the latter, but the former is effectively done 
already as it implicitly disables or breaks a load of features.

David