🚀 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.

There are more reasons why you can't use gcc 2.3.3 to build Appkit  
programs.  One is that Appkit classes are built on top of NeXT's  
Objective-C runtime library which is _different_ from GNU's Objective-C  
runtime library.  Another problem (as you mention above) is that gcc does  
not recognize @class, @protocol, nor does it support NeXT's Distributed  
Objects stuff.

> - 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.

The main issue I have found here is that NeXT's Objective-C++ compiler  
does not support the C++ 2.1 standard (it supports the C++ 2.0 standard I  
believe).  You should be able to compile _old_ (version 1.3.7) versions of  
libg++ using NeXT's Objective-C++ compiler.

This is how I understand things:

                                  TOOL
                  Compiler               GNU Library Version
               _________________________________________________
          2.0 | NeXT Objective-C++ | (1.37) or (1.39 w/ hacks?) |
C++ std.      |--------------------|----------------------------|
          2.1 | GNU 2.3.2 (2.3.3?) | 2.2                        |
              ---------------------------------------------------

> 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?

Since the GNU project seems uninterested in compat. w/ NeXT's  
Objective-C++ compiler and runtime (with Distrib. Obj., etc.), I think  
that the best we can hope for is that NeXT will bring Objective-C++ up to  
the C++ 2.1 standard so that we can compile the latest libg++ on NeXT.

PS Are nested function definitions part of the C++ 2.1 standard?  I  
believe that GNU's compiler allows these.  Does the GNU compiler have  
features outside the C++ 2.1 standard?  Does libg++ use any of these  
features?

> Paul F. Kunz	pfkeb@slac.stanford.edu (NeXT mail ok)

+--------------------------------+----------------------------------+
|          Bill Burcham          | "Make no small plans; they have  |
| First National Bank of Chicago | no magic to stir men's souls"    |
|    billb@fnbc.com  (NeXTmail)  |      Daniel J. Burnham           |
+--------------------------------+----------------------------------+