On Thu, Jul 07, 2005 at 12:02:40PM -0400, Chip Salzenberg wrote: > On Thu, Jul 07, 2005 at 10:43:45AM -0500, Patrick R. Michaud wrote: > > With something like > > > > .sub "foo" > > .param int beta > > .param string gamma :optional > > .param string delta :optional > > .param pmc epislon :slurpy > > > > So, all we really need is something that can tell us how many :optional > > arguments were filled in. > > ITYM "parameters". I know it's confusing, but at least for now, the > terminology is that arguments are passed and parameters are bound to > (or assigned) the argument values.
Yes, you're correct, no, it's not confusing -- I normally try to keep my use of the terms "argument" and "parameter" straight but just slipped here. :-| > If it would otherwise be necessary to keep state, it might be best > included right in the get_params/get_results opcodes. Say a new bit > ":opt_count", which means that the given register should be assigned > the count? > ... > Would that work for everyone? Yes, yes, yes! Especially since one of the first thing I'm going to have to do is assign the optional argument count into a register, it'd be fantastic if PIR could just do it for me and not have to worry about an opcode for it. Pm
