Did you put an eye on my implementation? what's the point in using computed goto when tracing, checking bounds or profiling?
Daniel Grunblatt. On Sun, 4 Nov 2001, Michael Fischer wrote: > On Nov 04, Brent Dax <[EMAIL PROTECTED]> took up a keyboard and banged out > > Michael Fischer: > > # In the goto case, we spin. And perhaps I am broken there. End > > # really wants to return, not just set the pc, but I hadn't thought > > # of a clever way to do that corner case, and wanted to see what > > # the behavior would be without it. I suspect I need it. > > > > Can't you just break()? > > Out of a function? > > In the goto case, I write a function conatining the array of > &&label_foo, and do a lot of gotos inside a while(1) loop. > Neither a 'break' nor a 'return' in the end op seems to be helping. > The function is declared to return void, so a 'return' at the > bottom of the function doesn't matter, really (yes, I tried it). > > all this followed by > > #define DO_OP(pc,interpreter) goto_op_dispatch((pc),(interpreter)) > > Sigh. > > What we _really_ want anyway, IMHO, is a not-compiler-specific > way to write the gotos. I have not the expertise at this time, > as I discovered to my chagrin after several hours of experimentation > yesterday. Cant use something like '5' as the goto label. Damn. > Enums didn't help matters. As mjd says, ingenuity is always in > short supply. More eyes? > > Michael > -- > Michael Fischer 7.5 million years to run > [EMAIL PROTECTED] printf "%d", 0x2a; > -- deep thought >
