Janne Jalkanen wrote:
The reason why those were made private was because the API should depend on the actual value of the strings, not the declared constants. It was a mistake to declare them public in the first place,.
I don't follow the logic of that at all. If I've got code that interacts with those constants (and they are constants), the "actual value of the strings" is the constant value, which I need access to programmatically.
It also ends up with duplicate documentation, which is always a bad thing (because if those two ever get out of sync...)
If the values are constants, declared final, then that can never happen. You've lot me here.
Besides, I figured nobody used them. Looks like was wrong...
Yes, I have declared PARAM_* values as constants on all my plugins as many, many, many of them are subclasses of subclasses, so I need to be able to programmatically grab the values. Declaring them private keeps that from happening. Murray ........................................................................... Murray Altheim <murray07 at altheim.com> === = = http://www.altheim.com/murray/ = = === SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = = Boundless wind and moon - the eye within eyes, Inexhaustible heaven and earth - the light beyond light, The willow dark, the flower bright - ten thousand houses, Knock at any door - there's one who will respond. -- The Blue Cliff Record
