#179: LIST-DIRECTORY ignores :RESOLVE-SYMLINKS flag?
-----------------------------------------------------------+----------------
Reporter: mevenson | Owner: somebody
Type: defect | Status: new
Priority: minor | Milestone: unscheduled
Component: other | Version: 1.0
Keywords: list-directory platform-dependence unanalyzed |
-----------------------------------------------------------+----------------
I think there is a bug in the list-directory function. The resolve-
symlinks flag seems to always resolve the directory symlinks even when the
flag is set to nil.
Let's have a directory as :
total 4
drwxr-xr-x 2 bege users 4096 Oct 23 23:52 dir
lrwxrwxrwx 1 bege users 3 Oct 23 23:53 dir-link -> dir
-rw-r--r-- 1 bege users 0 Oct 23 23:53 file
lrwxrwxrwx 1 bege users 4 Oct 23 23:53 file-link -> file
Then
Armed Bear Common Lisp 0.26.2
Java 1.6.0_26 Sun Microsystems Inc.
Java HotSpot(TM) 64-Bit Server VM
Low-level initialization completed in 1.436 seconds.
Startup completed in 5.385 seconds.
Type ":help" for a list of available commands.
CL-USER(1): (directory "./*" :resolve-symlinks nil)
(#P"/home/bege/TEST/./file" #P"/home/bege/TEST/dir/" #P"/home/bege/TEST
/./file-link" #P"/home/bege/TEST/dir/")
Sorry, if this has been already fixed...
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/179>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#178: Replace source path with logical pathnames
--------------------------------------------------------------+-------------
Reporter: mevenson | Owner: somebody
Type: enhancement | Status: new
Priority: minor | Milestone: unscheduled
Component: other | Version: 1.0
Keywords: fasl bite-sized logical-pathname source metadata |
--------------------------------------------------------------+-------------
It would reduce the fasl sizes somewhat to refer to the path as a logical
pathname.
This is a suitable "bite-sized" excercise to new contributors to ABCL.
Simply figure out how to get the compiler to emit logical pathnames
referring to [sys;src], and ensure the proper path is recorded in
'system.lisp' at build time.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/178>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#143: CLOSURE-HTML 20101006-git fails to compile
------------------------------------+---------------------------------------
Reporter: mevenson | Owner: mevenson
Type: defect | Status: new
Priority: major | Milestone: 0.26
Component: libraries | Version: 0.24
Keywords: quicklisp closure-html |
------------------------------------+---------------------------------------
Attempting to install closure-html from Quicklisp produces a stack
overflow when the compiler attempts to process the CLEX:DEFLEXER SGML:DTD
form on line 89 of "src/parse/sgml-dtd.lisp".
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/143>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#84: jcall and t/nil boolean arguments
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: java | Version:
Keywords: |
------------------------+---------------------------------------------------
Can it be made so that within jcall, t or nil is understood as a java
boolean argument?
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/84>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#115: Generate specific classes for compiled Go/Return
-------------------------+--------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: enhancement | Status: new
Priority: major | Milestone:
Component: compiler | Version:
Keywords: |
-------------------------+--------------------------------------------------
By using specific classes for Go/Return, we could make our exception
handling more targetted; there would be no sifting through all the
unwinding levels for the right level (unpacking the 'return-tag' or 'go-
tag').
Instead, the jump would hit all the finally clauses without further
checking; straight through to the right handler.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/115>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#121: p2-test-* infrastructure should use COMPILE-TEST-FORM
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: defect | Status: new
Priority: major | Milestone:
Component: compiler | Version:
Keywords: |
------------------------+---------------------------------------------------
Where it sometimes uses COMPILE-FORM and tests for NIL.
Another idea is to use FAIL/SUCCESS labels as argument to the compile-
test-function, which may result in more more efficient code. For example,
in that case, a NOT compilation only requires reversing the labels.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/121>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#134: Better support for packaging systems in jar files
--------------------------------+-------------------------------------------
Reporter: mevenson | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone: 0.26
Component: java | Version:
Keywords: asdf jar packaging |
--------------------------------+-------------------------------------------
Meta ticket for collecting requirements for packaging systems in jar
files. Currently support exists for loading ASDF2 systems as source
packaged in a jar (see ABCL's contrib via the Ant target 'abcl.contrib'),
but additional support is often requested.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/134>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#135: ql:FEB2011:bordeaux-threads BORDEAUX-THREADS does not work
------------------------------------------------+---------------------------
Reporter: mevenson | Owner: mevenson
Type: defect | Status: new
Priority: major | Milestone: 0.25
Component: libraries | Version: 0.24
Keywords: bordeaux-threads quicklisp threads |
------------------------------------------------+---------------------------
[http://common-lisp.net/project/bordeaux-threads/ bordeaux-threads] fails
with ABCL due to a number of reasons for which I am in progress of working
through patches. This issue will track the status of these patches
against the progress of those patches against both [http://common-lisp.net/gitweb?p=projects/bordeaux-threads/bordeaux-threads.git;a=summary
BORDEAUX-THREADS in git] and [http://www.quicklisp.org/beta/ the version
distributed with QuickLisp] (the version of FEB2011 as of this writing).
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/135>
armedbear <http://common-lisp.net/project/armedbear>
armedbear