RFR 8194746: (fs) Add equivalents of Paths.get to Path interface

Roger Riggs roger.riggs at oracle.com
Thu Mar 15 15:47:08 UTC 2018


Hi Brian,

yes,   (though I would use "may" instead of "might")

Thanks, Roger


On 3/15/18 11:44 AM, Brian Burkhalter wrote:
>
> On Mar 15, 2018, at 7:22 AM, Alan Bateman <Alan.Bateman at oracle.com 
> <mailto:Alan.Bateman at oracle.com>> wrote:
>
>> On 15/03/2018 14:05, Roger Riggs wrote:
>>> Hi Alan,
>>>
>>> Perhaps then, say it "may be deprecated"... instead of "obsolete".
>>> or lead the api note with the recommendation to use Path.of.
>> That seems a good idea.
>
> Would this be reasonable (in Paths class doc)?
>
>  * @apiNote
>  * As of JDK 11, it is recommended to obtain a {@code Path} via the
>  * {@code Path.of} methods instead of via the {@code get} methods 
> defined in
>  * this class as this class might be deprecated.
>
> Thanks,
>
> Brian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20180315/e5fa43fb/attachment.html>


More information about the nio-dev mailing list