December 2012 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #133: Mixed case inconsistency in TRANSLATE-LOGICAL-PATHNAMES
by armedbear 09 Dec '12

09 Dec '12

#133: Mixed case inconsistency in TRANSLATE-LOGICAL-PATHNAMES -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 0.25 Component: interpreter | Version: 0.24 Keywords: | -------------------------+-------------------------------------------------- Jonathan Boca reports {{{ As the following code and transcript demonstrate, translate-logical-pathname appears to be downcasing paths inconsistently: ;;; test.cl (setf (logical-pathname-translations "foo") '(("foo:bar;*.lisp" "/FooRoot/bar/*.lisp") ("foo:*.lisp" "/FooRoot/*.lisp"))) ;;; In the following pathname translation, the entire path is downcased (pprint (translate-logical-pathname "foo:bar;foobar.lisp")) ;;; In each of the next two, the entire path EXCEPT for the host is downcased -- ;;; the host is unchanged (pprint (translate-logical-pathname "foo:foobar.lisp")) (pprint (translate-logical-pathname "foo:Foobar.lisp")) --- Armed Bear Common Lisp 0.24.0 Java 1.6.0_22 Apple Inc. Java HotSpot(TM) Client VM Low-level initialization completed in 0.478 seconds. Startup completed in 1.386 seconds. Type ":help" for a list of available commands. CL-USER(1): (load "test.cl") #P"/fooroot/bar/foobar.lisp" #P"/FooRoot/foobar.lisp" #P"/FooRoot/foobar.lisp" T CL-USER(2): --- SBCL and CLISP both produce the following output for the above code: #P"/FooRoot/bar/foobar.lisp" #P"/FooRoot/foobar.lisp" #P"/FooRoot/foobar.lisp" Allegro's ALISP and MLISP both produce the following: #P"/FooRoot/bar/foobar.lisp" #P"/FooRoot/foobar.lisp" #P"/FooRoot/Foobar.lisp" }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/133> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 11

[armedbear-ticket] [armedbear] #180: stack overflow with lparallel
by armedbear 09 Dec '12

09 Dec '12

#180: stack overflow with lparallel ---------------------------------------------------------+------------------ Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: unscheduled Component: other | Version: 1.0 Keywords: lparallel stack-overflow jvm multi-threaded | ---------------------------------------------------------+------------------ With the [http://lparallel.com very interesting lparallel library], ABCL can get into some stack overflow situations (especially on newer JVM implementations). Also, I get the feeling that the BORDEAUX-THREADS mapping for ABCL is not optimal, as when I run LPARALLEL full out on a many worker kernel, I don't maximize the actual available CPU/RAM on a multicore x64 system. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/180> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #244: compile doesn't return correct values for warnings-p and failure-p
by armedbear 09 Dec '12

09 Dec '12

#244: compile doesn't return correct values for warnings-p and failure-p ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: compiler | Version: Keywords: | ------------------------+--------------------------------------------------- (compile nil '(lambda () (char=))) ; Caught WARNING: ; Wrong number of arguments for CHAR=. ; Compilation unit finished ; Caught 1 WARNING condition #<FUNCTION (LAMBDA ()) {456E3EB3}> NIL NIL while it should be T, T. jvm-compile, which handles this doesn't succeed because the underlying with-compilation-unit eats all the warnings and errors so that jvm-compile's handler-bind doesn't get a piece of them. Binding *resignal-compiler-warnings* to T inside jvm-compile resolves this. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/244> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #169: Conformance with section 3.2.4.4 (externalized objects in COMPILE-FILE)
by armedbear 09 Dec '12

09 Dec '12

#169: Conformance with section 3.2.4.4 (externalized objects in COMPILE-FILE) ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | ------------------------+--------------------------------------------------- Currently, if the same object is encountered in multiple forms being compiled, that object is externalized on each encounter. The spec requires that identical objects in the source be identical in the compiled file as per the first sentence of [http://www.lispworks.com/documentation/HyperSpec/Body/03_bdd.htm section 3.2.4.4]. As a consequence, we'll need an ''object table'' of some kind, allowing the object to be referenced further down in the file compilation. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/169> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #132: Inconsistent use of :case :common for pathnames
by armedbear 09 Dec '12

09 Dec '12

#132: Inconsistent use of :case :common for pathnames -------------------------+-------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 0.25 Component: interpreter | Version: 0.24 Keywords: | -------------------------+-------------------------------------------------- Pascal Bourguignon notes: {{{ CLHS says: 19.2.2.1.2.2 Common Case in Pathname Components For the functions in Figure 19-2, a value of :common for the :case argument that these functions should receive and yield strings in component values according to the following conventions: * All uppercase means to use a file system's customary case. * All lowercase means to use the opposite of the customary case. * Mixed case represents itself. Note that these conventions have been chosen in such a way that translation from :local to :common and back to :local is information-preserving. [pjb@kuiper :0.0 lisp]$ abcl Armed Bear Common Lisp 0.20.0 Java 1.6.0_22 Sun Microsystems Inc. Java HotSpot(TM) Server VM Low-level initialization completed in 0.265 seconds. Startup completed in 0.718 seconds. Type ":help" for a list of available commands. CL-USER(1): (make-pathname :name "TEST" :type "LISP" :case :common) #P"TEST.LISP" CL-USER(2): (namestring (make-pathname :name "TEST" :type "LISP" :case :common)) "TEST.LISP" I'm on a linux system on a ext3 file system. The customary case is lower case (case significant on this particular file system, but 99.999% of the files on unix are lower case). Therefore I would expect to get #P"test.lisp" Notice that: (make-pathname :name "test" :type "lisp" :case :common) should produce #P"TEST.LISP" and that: (make-pathname :name "Test" :type "Lisp" :case :common) should produce #P"Test.Lisp" }}} {{{ Mark Evenson writes: > > On 11/7/10 5:02 AM, Pascal J. Bourguignon wrote: >> >> >> >> CLHS says: >> >> >> >> 19.2.2.1.2.2 Common Case in Pathname Components >> >> >> >> For the functions in Figure 19-2, a value of :common for the :case >> >> argument that these functions should receive and yield strings in >> >> component values according to the following conventions: >> >> >> >> * All uppercase means to use a file system's customary case. >> >> * All lowercase means to use the opposite of the customary case. >> >> * Mixed case represents itself. >> >> >> >> Note that these conventions have been chosen in such a way that >> >> translation from :local to :common and back to :local is >> >> information-preserving. > > > > What an odd corner of the CLHS, littered with the bones of extinct > > filesystems! This behavior that seems like it would produce > > unpleasantries much more than it would help anyone, violating the > > principle of least surprise. But we claim that ABCL will be ANSI first > > and foremost, so I guess we have to pay attention here… I should mention that I use routinely logical pathnames, and they work very well, on all implementations that conformantly implement them. That means that all my logical pathnames are always upcase letters, and no special symbols (apart from an occasional dash). I understand that using implementation dependant syntax (special characters, lower-case, mixed-case) in logical pathnames can lead to surprises, but I avoid them. Now, it's not a question of extinct file systems. You still have to deal with at least two different major syntaxes: POSIX and MS-Windows/MS-DOS. I just cannot use in programs that will have to run on both Linux or MacOSX and MS-Windows physical pathname literals, because they don't use the same syntax. On the other hand, #P"HOME:SRC;LISP;EXAMPLE.LISP" can be translated to either #P"C:\\Users Files\\Pascal\\src\\lisp\\example.lisp" or #P"/home/pjb/src/lisp/example.lisp" portably on these targets. The point for an implementation is to know what it's targets are, and to implement proper behavior when translating and merging logical pathnames. You must be careful when merging logical pathnames with physical pathnames, notably when it's done in make-pathname: the :case parameter must have effect only on the new strings, not on the :defaults parameter. > > I suppose there is no definition of "customary case", huh? Indeed. > > Pascal suggests a notion of filesystem statistics ("99.999% of files > > are lowercase") but for a developer dealing with lots of Java files > > this isn't very releavant. Does Java provide its own file system, or does it map to the host file system? Notice that logical pathnames don't have to be able to represent all the physical pathnames, without an explicit translation. If you have a file system that is case sensitive, then you may write: (setf (logical-pathname-translations "APP") (list (list #P"APP:EXAMPLE;FILE.LISP" #P"/MyApp/Example/File.lisp") (list #P"APP:EXAMPLE;ANOTHER-FILE.LISP" #P"/MyApp/Example/AnotherFile.lisp") (list #P"APP:EXAMPLE;*.DATA" #P"/MyApp/Example/*.appdata") (list #P"APP:EXAMPLE;SOME-MODULE.*" #P"/MyApp/Example/SomeBigModule.*") (list #P"APP:APP.CONFIGURATION" #P"/MyApp/.config") (list #P"APP:CUSTOMARY;**;*" #P"/MyApp;**;*") (list #P"APP:CUSTOMARY;**;*.*" #P"/MyApp;**;*.*"))) to be able to access to files with strange physical names. The question indeed is to decide what is the customary case. You can choose uppercase or you can choose lowercase. This matters only for file systems that are case sensitive, but even file systems that are not case sensitive, such as MS-DOS, have a prefered way to display the names. > > Lacking a more precise definition, I would then advocate that we declare > > lowercase to be the customary case across UNIX, OSX, and Windows for > > ABCL, patching our behavior accordingly. That would be good. > > I thought briefly about advocating Windows to have "uppercase" as its > > customary case, but that is only really true in a DOS world which > > "modern" Windows systems really aren't any more. Yes. > > And although we theoretically run on JVMs on say VMS, if we run into > > such needs, we might devote a user-accessible special variable to > > control the implementation. This is also a good option. }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/132> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 10

[armedbear-ticket] [armedbear] #248: More clear error handling for toString throwing an exception
by armedbear 09 Dec '12

09 Dec '12

#248: More clear error handling for toString throwing an exception --------------------------------------------+------------------------------- Reporter: https://openid.fau.de/eg74yneg | Owner: ehuelsmann Type: enhancement | Status: new Priority: major | Milestone: Component: interpreter | Version: Keywords: | --------------------------------------------+------------------------------- For some class *test* imported from Java {{{ PKG> (#"toString" *test*) ; Evaluation aborted on #<JAVA-EXCEPTION java.lang.NullPointerException {FD82F5}>. PKG> *test* ; Evaluation aborted on NIL. }}} so the second form could include some indication on what goes wrong especially as toString is called fairly regular in a interactive LISP session -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/248> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #197: JAR-PATHNAME errors and ambiguities
by armedbear 09 Dec '12

09 Dec '12

#197: JAR-PATHNAME errors and ambiguities --------------------------+------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.1.0 Component: interpreter | Version: 1.0.1 Keywords: jar-pathname | --------------------------+------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2200 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. 2. 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" }}} 3. 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" }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/197> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #233: Evaluation of (DIRECTORY "/*/") fails
by armedbear 09 Dec '12

09 Dec '12

#233: Evaluation of (DIRECTORY "/*/") fails ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: Component: libraries | Version: 1.1.0-dev Keywords: | ------------------------+--------------------------------------------------- Reported by Stas Boukarev on #abcl: (DIRECTORY "/*/") ---> #<THREAD "interpreter" {E2B9E5}>: Debugger invoked on condition of type TYPE-ERR OR The value NIL is not of type (OR PATHNAME STRING FILE-STREAM SYSTEM:JAR- STREAM SYSTEM:URL-STREAM). Restarts: 0: TOP-LEVEL Return to top level. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/233> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #239: defgeneric with unsuitable :generic-function-class gives incomprehensible error
by armedbear 07 Dec '12

07 Dec '12

#239: defgeneric with unsuitable :generic-function-class gives incomprehensible error -----------------------+---------------------------------------------------- Reporter: rschlatte | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: Component: (A)MOP | Version: Keywords: | -----------------------+---------------------------------------------------- Compiling and loading the following (incorrect) file gives an error saying that foo-generic-function is not of type standard-generic-function. The real error is that foo-generic-function must be defined with (:metaclass funcallable-standard-class) to be suitable as a generic function class. {{{ (require :clos) (defclass foo-generic-function (standard-generic-function)) (defgeneric goo (a b) (:generic-function-class foo-generic-function) (:method (a b) (princ "default method"))) (print #'goo) }}} The attached patch would emit a full warning in defgeneric, but currently find-class does not implement correct behavior when called with 3 parameters. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/239> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #242: Unused &key warnings in defmethod forms should not cause style-warnings
by armedbear 07 Dec '12

07 Dec '12

#242: Unused &key warnings in defmethod forms should not cause style-warnings -----------------------+---------------------------------------------------- Reporter: rschlatte | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: Component: compiler | Version: Keywords: | -----------------------+---------------------------------------------------- CLHS 7.6.5 says: "The lambda list congruence rules require that each method accept all of the keyword arguments mentioned after &key in the generic function definition, by accepting them explicitly, by specifying &allow-other-keys, or by specifying &rest but not &key." Currently, when compiling a file containing the form {{{(defmethod foo ((x fixnum) &key y z) x)}}} we get style warnings about unused variables y and z. I think that these style warnings can be safely elided, since a typo in the arglist will lead to another style warning "Undefined variable A assumed special". -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/242> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5