On Wednesday 27 September 2006 03:40, Leopold Toetsch wrote:

> Now compare this with an I/O opcode:
>
>   read S0, P0, 10   # PIO_reads(... P0 ...)
>
> If P0 isn't a ParrotIO opcode, this segfaults. See t/pmc/io_1.pir. While we
> could of course check, what type P0 is, such a check would be needed for
> every IO opcode. (And see below)

I don't buy this argument.  If the cost for checking the type of P0 is greater 
than the cost of doing IO, that's a big problem and not with the interface.

-- c

Reply via email to