On Fri, 6 Jul 2001, Dan Sugalski wrote:
> > > You've pretty much got it. The flag-checking will be hardwired, but
> > > there's no reason that the function called can't be user-defined.
> > > Being able to install an arbitrary number of user-defined inter-opcode
> > > (and inter-statement) functions seems to make sense, and I don't see
> > > it as incurring any extra costs, so... (As long as you don't mind that
> > > it doesn't necessarily happen in a truly compiled version of your
> > > program)
> >
> >Why wouldn't it get included in a compiled version? Optimization
> >issues? It seems to me that if I write a module that does profiling or
> >something, and the user includes it in their compile, they are saying, "I
> >understand the costs involved in polling for a callback between logical
> >operations, and I'm willing to accept those costs".
>
> When I said "truly compiled" I meant down to C, or via a TIL scheme,
> or straight to machine code. Things that go to bytecode will still be
> run through the opcode loop, which means that all the standard
> inter-op stuff will be available.
Yeah, that's what I meant too. But as long as there's seperation between
logical operations, you could still just insert the callbacks inline.
The only thing that I can think of that would prevent it, would be if more
than one opcode would be combined into a single operation that can't be
interrupted. But inter-statement function calls (which is a great idea by
the way) could still be inlined, couldn't they?
- D
<[EMAIL PROTECTED]>
