Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: stdarg: va_list pass by value?
Message-ID: <14628@smoke.brl.mil>
Date: 1 Dec 90 00:25:25 GMT
References: <136196@pyramid.pyramid.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 9

In article <136196@pyramid.pyramid.com> markhall@pyrps5.pyramid.com (Mark Hall) writes:
>Since the standard explicitly calls out the indeterminacy
>of passing AP objects as arguments, shouldn't it also call out the 
>indeterminacy of assigning AP objects?

It doesn't have to; since va_list may be an array type, a strictly-
conforming program must not attempt to copy by in an assignment
expression.  This leaves open the question whether or not one could
memcpy() it, but my advice is to not try such elaborate hackery.