TRANSLATE-PATHNAME doesn't translate when a complex pattern in SOURCE equals one in FROM.

Bug #1738550 reported by Richard M Kreuter on 2017-12-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

TRANSLATE-PATHNAME doesn't translate a complex wildcard (i.e., a PATTERN) in the SOURCE argument when the corresponding field in FROM is the same pattern:

$ sh ./ --no-userinit --no-sysinit
(running SBCL from: .)
This is SBCL, an implementation of ANSI Common Lisp.
More information about SBCL is available at <>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
* (translate-pathname #p"a*" #p"a*" #p"z*")


I expected #P"z*", though #P"za*" might also be conforming.

Don't have a solution to hand, but it's likely that SB-IMPL::TRANSLATE-COMPONENT should do something more advanced than merely returning SOURCE in this case.

Other required data:

$ uname -a
Darwin m5.localdomain 14.5.0 Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64

* *features*



To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers