[otj-users] [Bug ?]: static final constant in role not initialized/error

[Andreas Werner]

Hi Stephan,

in my situation, the declaration of the constant as a team field is even
a better solution, because it is used by roles in other teams, and as a
team field it is easier to access.

Thank you very much for this hint!

To answer your question: apart of this I can't currently guess another
situation where initializing via method might be useful...

Best Regards, Andreas


Stephan Herrmann wrote:
> 
> So currently, if you can't provide a static initialization expression (i.e., an
> expression that can safely be inlined), I must ask you to use a team field
> instead (static or non-static, you choose). 
> 
> Is that a major limitation?
> We could let the compiler do that for you (i.e., you write a static role field,
> the compiler transparently transforms it to a team member field), but that
> is quite an effort to pay, which I'd like to avoid at the current point.
> How important are static role fields beyond simple constants for you?
> (I'm asking every body on this list).
> 
> thanks for bringing this up,
> Stephan
>