John Zulauf wrote:
|                                                   ... I'm not sure what the
| problem would be dispatching to a generic noop in that case in terms of the
| call stack ( i must have missed that post) ...

If we assume that every function we might want to dispatch uses a
calling sequence in which the caller cleans up the stack (the normal
``extern C'' convention), then we don't have a problem.

On the other hand, a generic no-op function can't support a
callee-cleanup sequence, because it doesn't know how many operands to
pop off the stack.  So if for some reason we needed to dispatch
functions using callee-cleanup, we wouldn't be able to support a
generic no-op.  In that case an app that invokes a function that's
unsupported by the current rendering context would have to be
terminated.

As far as I know, only the first case applies to us, but since David
raised the issue I included it in my list.

Allen

Reply via email to