Proposal for Property Accessors

Remi Forax forax at univ-mlv.fr
Sat Jan 5 10:41:41 PST 2013


On 01/05/2013 07:37 PM, Noctarius wrote:
> Am 05.01.2013 19:15, schrieb BGB:
>> On 1/5/2013 10:17 AM, Noctarius wrote:
>>> Ok I took some time to make a deeper introduction in what I
>>> imagine to do:
>>> https://www.sourceprojects.org/default/2013/01/05/1357395720000.html
>>>
>>>
>>>
> As mentioned before it would be great if someone is interested in
>>> the topic and wants to help.
>> well, I guess this forum is more for JVM level stuff, whereas
>> all this is more a Java compiler level feature, but oh well...
>>
> But this feature would need JVM level support to make old code
> working. That's the most important feature from my point of view -
> you can just make the old public field a property and old external
> code does not needs to be recompiled. One idea would be to
> relocate the xload bytecode to the property accessor (maybe there
> would be a better way).

There is a better way, the load should be an invokedynamic so it can be 
wired to a getter or a field access depending on the implementation.

Now, the real question is what problem do you want to solve exactly ?

>
> Chris

Rémi



More information about the mlvm-dev mailing list