🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.next.programmer
3 messages
3 total messages Started by Reginald Perry Thu, 31 Dec 1992 00:44
Problems using gcc 2.3.3
#1997
Author: Reginald Perry
Date: Thu, 31 Dec 1992 00:44
54 lines
2675 bytes
I am having problems using gcc 2.3.3 on the NeXT which is an '040 cube
running NS 3.0. What follows is a snippet of the code followed by the
error. Any help at all would be greatly appreciated.


				Reggie


/* Protocol support */

@class Protocol;

struct objc_protocol_list {
	struct objc_protocol_list *next;
	int count;
	Protocol *list[1];
};

/NextDeveloper/Headers/objc/objc-class.h:77: invalid Objective C keyword `@class'
/NextDeveloper/Headers/objc/objc-class.h:77: parse error before `@class'
/NextDeveloper/Headers/objc/objc-class.h:82: parse error before `Protocol'
/NextDeveloper/Headers/objc/objc-class.h:82: warning: no semicolon at end of struct or union
-----------------------------------------------------------------------------
#ifdef __GNUC__
#ifndef __STRICT_ANSI__
__volatile	/* never returns */
#endif /* not __STRICT_ANSI__ */
#endif /* __GNUC__ */
extern void _NXRaiseError(int code, const void *data1, const void *data2);

/NextDeveloper/Headers/objc/error.h:81: warning: `extern' is not at beginning of declaration
-------------------------------------------------------------------------------
#import <objc/typedstream.h>
#import <objc/zone.h>
@class Protocol;

/NextDeveloper/Headers/objc/Object.h:17: invalid Objective C keyword `@class'
/NextDeveloper/Headers/objc/Object.h:17: parse error before `@class'
-----------------------------------------------------------------------------
- (BOOL) conformsTo: (Protocol *)aProtocolObject;
+ (BOOL) conformsTo: (Protocol *)aProtocolObject;

/NextDeveloper/Headers/objc/Object.h:69: parse error before `Protocol'
/NextDeveloper/Headers/objc/Object.h:70: parse error before `Protocol'
--------------------------------------------------------------------------

@protocol NXEncoding
// encode an objc (parameter) type
- encodeData:(void *)data ofType:(const char *)type;


/NextDeveloper/Headers/remote/transport.h:13: invalid Objective C keyword `@protocol'
/NextDeveloper/Headers/remote/transport.h:13: parse error before `@protocol'
/NextDeveloper/Headers/remote/transport.h:18: method definition not in class context
Re: Problems using gcc 2.3.3
#1999
Author: Darcy BROCKBANK
Date: Thu, 31 Dec 1992 03:02
15 lines
1024 bytes
In article <1htfq5INNhm3@shelley.u.washington.edu> reggie@stein.u.washington.edu (Reginald Perry) writes:
>I am having problems using gcc 2.3.3 on the NeXT which is an '040 cube
>running NS 3.0. What follows is a snippet of the code followed by the
>error. Any help at all would be greatly appreciated.
>
>
>				Reggie
>

Last thing I knew was that the latest version of gcc didn't support the
NeXT extensions to Objective-C in the 3.0 release of NeXTSTEP.

Forget trying to compile NeXTSTEP programs until this is implemented.

- db
Re: Problems using gcc 2.3.3
#2000
Author: Paul F. Kunz
Date: Thu, 31 Dec 1992 06:11
21 lines
1485 bytes
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?
--
Paul F. Kunz	pfkeb@slac.stanford.edu (NeXT mail ok)
Stanford Linear Accelerator Center, Stanford University
Voice: (415) 926-2884   (NeXT) Fax: (415) 926-3587
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads