More IO Changes (need feedback)

[James E Keenan]

On 11/21/12 8:26 PM, Andrew Whitworth wrote:
> Thanks for the tests, Jim. Yes, some failures are known and even
> expected. I don't want to start cleanup and details work until I get
> the go-ahead. I don't want to waste time on it if it's not the
> direction we want to go.
>

Yes, I figured that would be the case.  I leave to others more 
knowledgeable than I the evaluation of the go/no-go decision.

One thing:  Could you expand a bit on this?

 > 2) whiteknight/io_vtable_lookup In Parrot master, we lookup
 > information about the IO_VTABLE and the read/write IO_BUFFERs using
 > VTABLE_get_pointer_keyed_int. This is a bad system.

What specifically is bad about it?

jimk