🚀 go-pugleaf

In article <PFKEB.92Dec30221114@kaon.SLAC.Stanford.EDU>  
pfkeb@kaon.SLAC.Stanford.EDU (Paul F. Kunz) writes:
> So here we are...
> 
> - gcc 2.3.3 doesn't support NeXT's extensions to Objective-C which
> were introduced with NeXTSTEP3.0   So you can't use gcc for any
> compilation requiring the appkit; cuz it will hit things like 
> ``@class'' almost immediately.
> 
> - NeXT's cc++ doesn't support GNU's extension to the C++ language which
> were introduced with gcc 2.x.   So you can't use cc++ for any
> compilation requiring libg++; cuz it will hit things like
> ``#include-next stdlib.h'' almost immediately.
> 
> So if I understand things right (please correct me if I'm wrong), we
> are really in bad shape.   We can't use both the latest release of
> gcc/libg++ and NeXTSTEP 3.0 in the same application.
> 
> Anybody else find this distrubing?
YES,
and the question raises again 
WHY the hell can we not force NeXT to release it's changes to gcc.
They must release the source if they distribute the binaries.