Opened 5 years ago

Last modified 2 weeks ago

#197 accepted defect

JAR-PATHNAME errors and ambiguities

Reported by: mevenson Owned by: mevenson
Priority: critical Milestone: 1.6.0
Component: interpreter Version: 1.0.1
Keywords: jar-pathname user-feedback Cc:
Parent Tickets:

Description

Yong reports on armedbear@devel:

CL-USER> (make-pathname :device '("c:/a.b.jar")
              :directory '(:absolute "cl-ppcre"))
; Evaluation aborted on NIL.

Why am I not getting any errors (and not dropping into a debugger)? I
know the error is because the device is not a list of a pathname ie
missing a #P.

  1. What's printed out is not what was read in (trailing /)
    CL-USER> #P"jar:file:c:/a/b.jar!/cl-ppcre/"
    #P"jar:file:c:/a/b.jar!/cl-ppcre"
    
  1. Should this repeated jar:file:jar:file thing throw an error?
#P"jar:file:jar:file:c:/a/b.jar!/cl-ppcre/"
==> #P"jar:file:jar:file:c:/a/b.jar!/cl-ppcre"

Subtickets (add)

Change History (11)

comment:1 Changed 5 years ago by mevenson

  • Owner changed from ehuelsmann to mevenson
  • Priority changed from major to blocker
  • Status changed from new to accepted

comment:2 Changed 5 years ago by ehuelsmann

  • Keywords user-feedback added
  • Priority changed from blocker to critical

comment:3 Changed 5 years ago by mevenson

1) The only legal members of a DEVICE list are PATHNAMES.

You need to explicitly create a pathname via:

    (make-pathname :device '(#p"c:/a.b.jar")
              :directory '(:absolute "cl-ppcre"))

Agreed that an error would be a good idea.

comment:4 Changed 5 years ago by mevenson

  • Milestone changed from 1.1.0 to 1.1.1

Some issues have been addressed.

In general, the Pathname stuff need to be rewritten in Lisp.

comment:5 Changed 5 years ago by mevenson

  • Milestone changed from 1.1.1 to 1.2.0

comment:6 Changed 4 years ago by https://www.google.com/accounts/o8/id?id=AItOawkYnNNEAO_K40Gp0xROhyjOPgjvIskQ48M

  • Milestone changed from 1.2.0 to 1.3.0

comment:7 Changed 3 years ago by mevenson

  • Milestone changed from 1.3.0 to 2.0

Ticket retargeted after milestone closed

comment:8 Changed 3 years ago by mevenson

  • Milestone changed from 2.0 to 2.0.0

Milestone renamed

comment:9 Changed 3 years ago by mevenson

  • Milestone changed from 2.0.0 to 1.4.0

comment:10 Changed 9 months ago by mevenson

  • Milestone changed from 1.4.0 to 1.5.0

Ticket retargeted after milestone closed

comment:11 Changed 2 weeks ago by mevenson

  • Milestone changed from 1.5.0 to 1.6.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.