At 5:59 PM +0100 on 12/6/99, M. Uli Kusterer wrote: >>That'd take care of that one scenario, but there are a bunch more. And it >>still does not handle passing the environment to the "do" handler. > >Anthony, > > it'll need a pointer to the current stack anyway, to get its variable >values. Or what are you referring to? Varaibles aren't pushed on the stack. But the pointer can be passed (of course) but some special-casing of code will be required. Maybe it won't be so bad.
- OODL: Runtime Code Generation: Almost as evil as the secan... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as evil as ... M. Uli Kusterer
- Re: OODL: Runtime Code Generation: Almost as evil... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as ... M. Uli Kusterer
- Re: OODL: Runtime Code Generation: Almos... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as evil as... MP0werd
- Re: OODL: Runtime Code Generation: Almost as evil as... Paul Sutton
- Re: OODL: Runtime Code Generation: Almost as evi... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as... M. Uli Kusterer
- Re: OODL: Runtime Code Generation: Almos... DeRobertis
- Re: Re: Re: OODL: Runtime Code Generation: Almost ... MP0werd
- Re: Re: Re: OODL: Runtime Code Generation: Almost ... MP0werd
