The open opcode

[Andrew Whitworth]

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



On Thu, Apr 22, 2010 at 6:47 PM, chromatic <chromatic at wgz.org> wrote:
> On Thursday 22 April 2010 at 13:43, Jonathan Leto wrote:
>
>> Would it be possible to make the open opcode use the File or
>> FileHandle PMC behind the scenes? That would fix my problem and not
>> require changing anything to end users as well as avoiding the
>> deprecation cycle.
>
> How does that fix the problem?  I'm afraid I don't follow this step.
>
> -- c
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>