Why is the Java mapping for consts the way it is?

in Help Center
In the manual, the process for mapping from "const"s in a Slice file into Java is summarised as follows:
Why does it work that way? Is there any reason that all constants in a namespace can't be mapped "public static final" members of a single class, or something like that?
Just curious,
MEF
[E]ach Slice constant is mapped to a Java interface with the same name as the constant. The interface contains a member named value that holds the value of the constant.
Why does it work that way? Is there any reason that all constants in a namespace can't be mapped "public static final" members of a single class, or something like that?
Just curious,
MEF
0
Comments