[ CC'ed to list again ]

Sorry about that.

The subject of the thread was "calling convention abstraction". My
proposal was about one possible way to go, and I'd like to thank you for
the input. But there is much more then the one discussed issue.

I'd like to have HLL folks create a workable scheme for abstract and
extendible calling conventions that take all the various HLL-specific
extensions (*args, **kw, default values, Perl context, lisp variable
argument amount, tail calls...) into account. If each HLL does a
function or method call in a different way, we can forget any
interoperbility.

The current scheme is too limit and worse, as defined in terms of PASM,
not changable at all. This is a serious drawback for future changes and
optimization of the Parrot VM.

leo