Re: RFR: 5061061: SimpleDateFormat: unspecified behavior for reserved pattern letter [v2]

2025-03-27 Thread Justin Lu
On Mon, 24 Mar 2025 23:13:48 GMT, Justin Lu wrote: >> Please review this specification update for `SimpleDateFormat` which >> explicitly specifies the behavior for 'reserved' pattern letters. This is a >> specification update and has the potential low risk of making an >> implementation non-co

Re: RFR: 5061061: SimpleDateFormat: unspecified behavior for reserved pattern letter [v2]

2025-03-25 Thread Roger Riggs
On Mon, 24 Mar 2025 23:13:48 GMT, Justin Lu wrote: >> Please review this specification update for `SimpleDateFormat` which >> explicitly specifies the behavior for 'reserved' pattern letters. This is a >> specification update and has the potential low risk of making an >> implementation non-co

Re: RFR: 5061061: SimpleDateFormat: unspecified behavior for reserved pattern letter [v2]

2025-03-25 Thread Naoto Sato
On Mon, 24 Mar 2025 23:13:48 GMT, Justin Lu wrote: >> Please review this specification update for `SimpleDateFormat` which >> explicitly specifies the behavior for 'reserved' pattern letters. This is a >> specification update and has the potential low risk of making an >> implementation non-co

Re: RFR: 5061061: SimpleDateFormat: unspecified behavior for reserved pattern letter [v2]

2025-03-24 Thread Justin Lu
> Please review this specification update for `SimpleDateFormat` which > explicitly specifies the behavior for 'reserved' pattern letters. This is a > specification update and has the potential low risk of making an > implementation non-compliant. Thus, an associated CSR is filed. Justin Lu has

Re: RFR: 5061061: SimpleDateFormat: unspecified behavior for reserved pattern letter

2025-03-24 Thread Naoto Sato
On Mon, 24 Mar 2025 21:21:20 GMT, Justin Lu wrote: > Please review this specification update for `SimpleDateFormat` which > explicitly specifies the behavior for 'reserved' pattern letters. This is a > specification update and has the potential low risk of making an > implementation non-compli