Typo: n -> m

[Ekleog]

In §4.4.7.2, I think the number of values popped then pushed should be m: the number of return values, and not the number of argument values.

Am I correct?

[conrad-watt]

In §4.4.7.2 the n refers to the arity of the current frame F, which is derived from the length of the function return type. You can see in §4.4.7.1 that a frame is constructed with arity m when invoking a function.

It's not the same n as in §4.4.7.1, which does refer to the length of the function arguments.

[Ekleog]

Oh indeed, thanks! well, then suggestion: rename this n to a m, because changing the variable name at paragraph change is confusing, I being an example of its confusingness :)

[binji]

I think changing this case is fine, but this isn't an isolated case -- many places in the spec use the same variable name for different purposes. I'm curious if you found other places in the document where this was confusing.