Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site rabbit.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!alice!rabbit!ark
From: ark@rabbit.UUCP (Andrew Koenig)
Newsgroups: net.lang.c
Subject: Re: Varargs in C - (nf)
Message-ID: <3100@rabbit.UUCP>
Date: Wed, 29-Aug-84 13:50:11 EDT
Article-I.D.: rabbit.3100
Posted: Wed Aug 29 13:50:11 1984
Date-Received: Thu, 30-Aug-84 02:03:04 EDT
References: <13800005@smu.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 24

Perry (convex!smu!ppedz) proposes a way of handling variable
argument lists that he says is better than <varargs.h> because
it allows a stack frame to be passed to a subroutine.  Well,
so does <varargs.h>!  It is permissible to say, for example:

	#include <varargs.h>

	f (va_alist) va_dcl
	{
		va_list args;
		va_start (args);
		g (&args);
		va_end (args);
	}

	g (a) va_list *a;
	{
		int arg1;
		arg1 = va_arg (*a, int);
	}

<varargs.h> does not have any way of finding out the number
of arguments because it is extremely difficult to do that
in some implementations.