Re: RFR: 4668290: unclear spec for Polygon.bounds field [v4]

2022-12-07 Thread Alexey Ivanov
On Tue, 6 Dec 2022 21:33:33 GMT, SWinxy wrote: >> New documentation replaces the `This value can be null.`: >> >> When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, >> this becomes {@code null}. To get out of the null state, >> {@link #getBounds()} called with {@link #np

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v4]

2022-12-06 Thread Phil Race
On Tue, 6 Dec 2022 21:33:33 GMT, SWinxy wrote: >> New documentation replaces the `This value can be null.`: >> >> When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, >> this becomes {@code null}. To get out of the null state, >> {@link #getBounds()} called with {@link #np

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v4]

2022-12-06 Thread SWinxy
> New documentation replaces the `This value can be null.`: > > When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, > this becomes {@code null}. To get out of the null state, > {@link #getBounds()} called with {@link #npoints} being greater than > {@code 0} will transfer in

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v3]

2022-12-06 Thread Alexey Ivanov
On Fri, 30 Sep 2022 21:18:45 GMT, Phil Race wrote: >> SWinxy has updated the pull request incrementally with one additional commit >> since the last revision: >> >> Use javadoc code syntax for null > > src/java.desktop/share/classes/java/awt/Polygon.java line 111: > >> 109: * {@link #ge

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v3]

2022-12-06 Thread Alexey Ivanov
On Tue, 6 Dec 2022 01:18:24 GMT, SWinxy wrote: >> New documentation replaces the `This value can be null.`: >> >> When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, >> this becomes {@code null}. To get out of the null state, >> {@link #getBounds()} called with {@link #np

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v3]

2022-12-05 Thread SWinxy
> New documentation replaces the `This value can be null.`: > > When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, > this becomes {@code null}. To get out of the null state, > {@link #getBounds()} called with {@link #npoints} being greater than > {@code 0} will transfer in

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v2]

2022-12-05 Thread Alexey Ivanov
On Fri, 30 Sep 2022 21:30:25 GMT, SWinxy wrote: >> New documentation replaces the `This value can be null.`: >> >> When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, >> this becomes {@code null}. To get out of the null state, >> {@link #getBounds()} called with {@link #n

Re: RFR: 4668290: unclear spec for Polygon.bounds field [v2]

2022-09-30 Thread SWinxy
> New documentation replaces the `This value can be null.`: > > When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, > this becomes {@code null}. To get out of the null state, > {@link #getBounds()} called with {@link #npoints} being greater than > {@code 0} will transfer in

Re: RFR: 4668290: unclear spec for Polygon.bounds field

2022-09-30 Thread Phil Race
On Mon, 26 Sep 2022 02:27:53 GMT, SWinxy wrote: > New documentation replaces the `This value can be null.`: > > When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, > this becomes {@code null}. To get out of the null state, > {@link #getBounds()} called with {@link #npoint

RFR: 4668290: unclear spec for Polygon.bounds field

2022-09-25 Thread SWinxy
New documentation replaces the `This value can be null.`: When created, {@link #invalidate() invalidated}, or {@link #reset() reset}, this becomes {@code null}. To get out of the null state, {@link #getBounds()} called with {@link #npoints} being greater than {@code 0} will transfer into a non-nul