Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site hp-pcd.UUCP
Path: utzoo!linus!security!genrad!decvax!harpo!seismo!hao!hplabs!hp-pcd!hpfcla!hp-dcde!jack
From: jack@hp-dcde.UUCP
Newsgroups: net.micro.68k
Subject: Re: again, nargs - (nf)
Message-ID: <3640@hp-pcd.UUCP>
Date: Thu, 5-Jan-84 03:48:06 EST
Article-I.D.: hp-pcd.3640
Posted: Thu Jan  5 03:48:06 1984
Date-Received: Sat, 7-Jan-84 02:32:08 EST
Sender: notes_gateway@hp-pcd.UUCP
Organization: Hewlett-Packard, Fort Collins, CO
Lines: 20

#R:orstcs:8300002:hp-dcde:21100002:000:488
hp-dcde!jack    Jan  2 19:53:00 1984

The possible solution of examining the stack frame to determine nargs
has been suggested.  Consider this example:

main()
{
	alpha(1, beta(2,3,4), 5);
}

When beta is invoked, either the 1 or the 5 will have already been pushed
onto the stack in preperation for calling alpha (at least with our compiler).
Hence if beta just looks at main's stack frame, it will decide that four
arguments have been pushed for it.  Alas.


					-Jack "have McNelly do it" Applin
					(hplabs!hp-dcd!jack)