'instrumenting' arrays

I'm writing an STM called Multiverse
http://multiverse.codehaus.org

One of the things I want to add to one of the next releases is support
for transactional arrays. I already figured out how to deal with the
array itself;
if an transactional object has a field of type array of type X, I
upgrade the type of that field to: array of type transactional
reference of type X. This is
peanuts. I already got a prototype TransactionalArray working that
doesn't rely on instrumentation and lazily fills the array with
transactional references.
And I also got transactional references for primitives that reduce the
amount of boxing/unboxing.

The big problem is with the instrumentation of methods because it is
hard to figure out if the bytecode that accesses an array is touching
a normal array
or a transactional one. With GET_FIELD/PUT_FIELD this isn't a problem
because the instrumentation can determine based on the type of the
field owner
if something extra needs to be done. But in this case the context
matters and not the type.

So has someone experience with 'instrumenting' arrays?

-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws