The open opcode

[Jonathan Leto]

Howdy,

On Thu, Apr 22, 2010 at 4:34 PM, Andrew Whitworth <wknight8111 at gmail.com> wrote:
> the open opcode calls src/io/api.c:Parrot_io_open, which does redirect
> to the appropriate PMC type. We've done some encapsulation-breaking
> for performance issues (saves a PCC call if we can just muck with
> FileHandle's internals directly). In any case, the PMC is in control.
> So it's a moot point to wonder whether making the open opcode use the
> PMC would be an improvement for security or not: we do it anyway.
>
> --Andrew Whitworth
>

The issue I am getting at is that the the encapsulation-breaking makes
it so that when I override the File/FileHandle PMC's, the open opcode
still knows how to call the originals. Can we make the open opcode
actually look up the File/FileHandle PMC in the current interpreter?

Duke


-- 
Jonathan "Duke" Leto
jonathan at leto.net
http://leto.net