Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!qantel!lll-lcc!lll-crg!seismo!brl-adm!brl-smoke!smoke!see@NTA-VAX.ARPA
From: see@NTA-VAX.ARPA (Stein-Erik Engbr}ten)
Newsgroups: net.lang.c
Subject: Include the va_end!
Message-ID: <375@brl-smoke.ARPA>
Date: Tue, 29-Apr-86 04:43:38 EDT
Article-I.D.: brl-smok.375
Posted: Tue Apr 29 04:43:38 1986
Date-Received: Fri, 2-May-86 22:53:33 EDT
Sender: news@brl-smoke.ARPA
Lines: 22

In message <5336@alice.uUCp> Andrew Koenig (<ark@alice.uucp>)
writes:

>> I assume va_start be done in the original function.  (Dito the first
>> va_alist comment.)  Does va_end have to be done in the original
>> function also?  (va_end does nothing in my implementation.)
>
>It should be.  (va_end does nothing in every implementation I've seen)

I have found an implementation which needs the va_end. It caused
me a great deal of trouble - the source I was compiling (the 
SYSTEM_V source for curses!) had left out the va_end ("It doesn't
do anything, so why bother...").

The implementation is on the Pyramid 90x machine, the System V
part of it (it runs both 4.2 and System V at the same time!), 
where va_end is defined to be an '}'.

So please, everybody - even if 'nobody' defines the va_end,
include it all the same!

Stein-Erik Engbr}ten