On 1/6/2013 6:52 AM, Noctarius wrote:
> Am 06.01.2013 11:35, schrieb BGB:
>> On 1/6/2013 3:19 AM, Noctarius wrote:
>>> Am 06.01.2013 00:44, schrieb John Rose:
On Jan 5, 2013, at 12:03 PM, Remi Forax wrote:
> I think I prefer a more general mechanism that ask javac
> to replace all
Am 06.01.2013 11:35, schrieb BGB:
> On 1/6/2013 3:19 AM, Noctarius wrote:
>> Am 06.01.2013 00:44, schrieb John Rose:
>>> On Jan 5, 2013, at 12:03 PM, Remi Forax wrote:
>>>
I think I prefer a more general mechanism that ask javac
to replace all access to fields (or methods) for a given
>>
Am 06.01.2013 11:22, schrieb Jochen Theodorou:
> To drive the language list down there further I name the Groovy
> variant... fully aware that it is not likely something for Java at all.
> In Groovy we do:
>
> class Egg {
>int color
> }
>
> This will generate a getColor and a setColor metho
On 1/6/2013 3:19 AM, Noctarius wrote:
> Am 06.01.2013 00:44, schrieb John Rose:
>> On Jan 5, 2013, at 12:03 PM, Remi Forax wrote:
>>
>>> I think I prefer a more general mechanism that ask javac to
>>> replace all access to fields (or methods) for a given class,
>>> insert an invokedynamic instead a
To drive the language list down there further I name the Groovy
variant... fully aware that it is not likely something for Java at all.
In Groovy we do:
class Egg {
int color
}
This will generate a getColor and a setColor method, just like you
expect from the Java Bean Spec. You can still w
Am 05.01.2013 22:47, schrieb BGB:
> On 1/5/2013 2:20 PM, Noctarius wrote:
>> Am 05.01.2013 20:44, schrieb BGB:
>>> On 1/5/2013 12: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 w
Am 06.01.2013 00:44, schrieb John Rose:
> On Jan 5, 2013, at 12:03 PM, Remi Forax wrote:
>
>> I think I prefer a more general mechanism that ask javac to
>> replace all access to fields (or methods) for a given class,
>> insert an invokedynamic instead and let you specifies the
>> bootstrap metho
