When IKVM translates Java enums or static fields to CLI public properties and private fields with the same name are created. When trying to use the properies Boo emits an error:
....
print simfin.finance.product.Currency USD
When IKVM translates Java enums or static fields to CLI public properties and private fields with the same name are created. When trying to use the properies Boo emits an error:
....
print simfin.finance.product.Currency USD
gives:
Ambiguous reference 'USD': simfin.finance.product.Currency USD, simfin.finance.product.Currency USD.
(IronPython handles this case correctly)
I don't have access to that java lib to test, but could you try passing the -strictfinalfieldsemantics option to ikvmc and see if boo works then? I'm not sure if that will work though.
But it is strange that IKVM does that, since even C# doesn't allow you create a method or property with the same name as an existing field.
Doug H added a comment - 08/Sep/05 08:46 PM I don't have access to that java lib to test, but could you try passing the -strictfinalfieldsemantics option to ikvmc and see if boo works then? I'm not sure if that will work though.
But it is strange that IKVM does that, since even C# doesn't allow you create a method or property with the same name as an existing field.
Bug
Open
Major
Ambiguous reference when some public propery has same name as private field
But it is strange that IKVM does that, since even C# doesn't allow you create a method or property with the same name as an existing field.