The implication of the JDK-8194154 fix in jdk8u342.

[Thorsten Glaser]

On Thu, 21 Jul 2022, Sergey Bylokhov wrote:

> I have created the jbs bug to track the current issue:
> https://bugs.openjdk.org/browse/JDK-8290832
> if the community agrees to fix it in the OpenJDK repo I can propose the PR.

Given OpenJDK 8 is “legacy use only” it definitely should, IMHO,
continue running programs it used to run.

I’d rather question the proposed fix. It would be better to
normalise the paths at the places they are used.

One caveat: Martin Buchholz said that “ All APIs on Posix systems should
treat a sequence of more than one '/' equivalently to exactly one.” but
that’s untrue for one specific case: a sequence of exactly two (no less,
no more) leading slashes, in an absolute pathname, must be kept exactly
that becaude it *may* (but doesn’t have to) refer to a different filesy‐
stem namespace (e.g. UNC names, for networking) instead.

So, ///foo and ////foo are /foo but //foo may or may not be /foo.

Might be useful, even, to change 11 to match.

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

                        ****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also,     https://www.tarent.de/newsletter
╱ ╲ header encryption!
                        ****************************************************