On Wed, Aug 20, 2003 at 02:05:19PM +0200, Leopold Toetsch wrote: > This leads to changes in parsing the vtable.tbl - which we need anyway > to do the proposed var/value split of vtables. > > e.g. > [FETCH] > get_integer > ... > [STORE] > set_integer > ... > [PUSH] > push_integer > ... > and so on. > The section names conform (where applicable) to methods described in > Tie::*(3pm). > > Comments welcome
It's been noted that FETCHSLICE/STORESLICE are missing from the perl5 tied hash API, but that adding them at this stage would cause subtle bugs: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-11/msg02044.html Could we split the vtable further, so var/value by read/write, which would allow constant objects to swap their write vtable to a throw implementation. Did I misread what you were suggesting either in this message or later, and you were suggesting this split? I'm not sure if a simple read/write split also helps PMCs shared across threads. Maybe sharing between threads is a whole new can of worms that we should leave untouched for now. Nicholas Clark
