Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

erroneous `undefined type' messages

1 view
Skip to first unread message

Ken Raeburn

unread,
Aug 3, 1989, 10:35:17 PM8/3/89
to

Configuration: version 1.35 on VAX; experimental 1.35.95 on IBM RT/PC;
ancient 1.26 shipped with NeXT 0.9; version 1.35 on Sun-3.

Source file:

struct clist {
int c_cc;
};

int buf_maxchar = sizeof (struct cblock *);

buf_open(
#if ! SIGNAL
si
#endif
)
{
extern struct clist *b;
b->c_cc = 0;
}

On the NeXT, "cc" (their version of gcc) does not complain.

On the vax, sun, and RT, when SIGNAL is not defined:

buf_emul.c: In function buf_open:
buf_emul.c:14: invalid use of undefined type `struct clist'

When SIGNAL is defined, no messages result on the vax or sun. If
"struct cblock *" is replaced with a known type, no messages result.
(The RT one has other problems possibly due to local changes.)

-- Ken

KP KP

unread,
Aug 14, 2022, 1:08:53 PM8/14/22
to
That is a good observation.
0 new messages