<i18n dev> RFR: 8253459: Formatter treats index, width and precision > Integer.MAX_VALUE incorrectly [v7]

[Ian Graves]

On Tue, 6 Oct 2020 19:10:46 GMT, Ian Graves <igraves at openjdk.org> wrote:

>> Is the new exception type useful?  yes, it matches the previous pattern.
>> But it does not (and none of the IllegalFormatException subclasses) produce a readable message with the offending value. So the developer will not see anything useful.
>> The fine grained exceptions provide little value.
>
> I've been on the fence about this, personally. The Formatter uses pretty fine-grained exception types for error conditions. I'd be okay discontinuing this practice here, but am not sure what to replace this with. Perhaps we enable `IllegalFormatException` to be, itself, public and instantiable ?

Updates (including cleaning up some git weirdness with rebasing) include adherence to the new CSR draft proposal. This makes the new exception type package-private.

-------------

PR: https://git.openjdk.java.net/jdk/pull/516