[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug?
From: |
glen e. p. ropella |
Subject: |
bug? |
Date: |
Wed, 16 Oct 1996 08:05:18 -0600 |
Ted,
Sorry it's taken me so long to respond. I've generated a bug
report (b001) for the use of the return value from va_start.
You'll have to forgive the "simple" nature of our bug tracking
system. We just now implemented it. [grin]
And, I've put it in the queue for the FAQ.
Thanks.
glen
-------------------------------b001-------------------------------------
Bug: void value not ignored as it ought to be in src/defobj/Symbol.m
Version Numbers: Swarm-961002
Status: Open
Priority: low
Assignee:
Date Reported: 10/05/96
Date Opened: 10/16/96
Date Closed:
Description:
First, I think I found a bug in the file src/defobj/Symbol.m. gcc
complained that "void value not ignored as it ought to be" on lines 119 and
142. Both lines are the same:
argptr = va_start( argptr, eventData );
According to Harbison & Steele (4th ed., p. 296), va_start is declared as:
void va_start(va_list ap, type);
I changed both lines to:
va_start( argptr, eventData );
and the file compiled fine.
Fix:
119c119
< argptr = va_start( argptr, eventData );
---
> va_start( argptr, eventData );
142c142
< argptr = va_start( argptr, eventData );
---
> va_start( argptr, eventData );
But, it is probably recommended that we use
(void) va_start(...) to indicate that the return value is
conciously unused. --gepr
Deadline: Next release of defobj library
- bug?, Theodore C. Belding, 1996/10/05
- bug?,
glen e. p. ropella <=