On Oct 09, Michael Maraist <[EMAIL PROTECTED]> took up a keyboard and banged out
> > void
> > runloop(int**code) {
> > static void* array[] = { &&op_end, &&op1, &&op2 };
> >
> > start:
> > goto *array[*code];
> >
> > op1:
> > foo; goto start;
> >
> > op2:
> > foo; goto start;
> >
> > op_end:
> > return;
> > } // end code
Declaring that static void * array[] = {...} in a header,
produced by process_opfunc.pl. Dan, Michael, Bryan,
care for me to revamp my patch to print out a goto
table like the above?
Dan, so out of all this, will vtable funcs have to be
represented in basic_opcodes.ops, or are they above all
that, and conversions (if any) done elsewhere? Or, more
cogently (*cough*), is the method of writing more stuff
in basic_opcodes.ops and letting the perl scripts handle
the conversion to C code still valid regardless of what
we do with vtables, modules, etc.?
Or will that stuff call for a change to the design of
those perl scripts, and the .ops file?
Michael Fischer
--
Developer, "Beware of bugs in the above code.
[EMAIL PROTECTED] I have only proven it correct, not tested it."
[EMAIL PROTECTED] -- Donald Knuth
