#444: Attempt to throw to the nonexistent tag DUPLICATABLE-CODE-P ???
-------------------------+----------------------
Reporter: aruttenberg | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: (A)MOP | Version:
Keywords: | Parent Tickets:
-------------------------+----------------------
(ext::macroexpand-all
'(loop for a = (sort foo 'string-lessp :key #'(lambda(x) x ))
for b = nil then 1
))
;;
;; Error compiling /Users/lori/repos/slime/swank/abcl.lisp:
;; Attempt to throw to the nonexistent tag DUPLICATABLE-CODE-P.
--
Ticket URL: <http://abcl.org/trac/ticket/444>
armedbear <http://abcl.org>
armedbear
#417: Bug in CL:DESTRUCTURING-BIND
---------------------------------------------+------------------------
Reporter: mevenson | Owner:
Type: defect | Status: new
Priority: major | Milestone: 1.5.0
Component: interpreter | Version:
Keywords: github-issue ansi-compatibility | Parent Tickets:
---------------------------------------------+------------------------
{{{
(defun test (args) (destructuring-bind (a b &rest c) args (list a b)))
(test '(1))
-> '(1 nil)
}}}
should signal an error
without the &rest args
{{{
(defun test (args) (destructuring-bind (a b) args (list a b)))
(test '(1))
}}}
signals an error as expected
Initial report on Github from Alan
<https://github.com/armedbear/abcl/issues/8>.
--
Ticket URL: <http://abcl.org/trac/ticket/417>
armedbear <http://abcl.org>
armedbear
#446: bogus type specifiers are allowed in handler-bind cases
----------------------+----------------------------
Reporter: charmon | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: compiler | Version: 1.5.0-dev
Keywords: | Parent Tickets:
----------------------+----------------------------
The following should give an error:
(handler-case
(error "what")
(bogus-error ()
(format nil "I'm sorry")))
bogus-error is an undefined type and ABCL should give an error instead of
silently ignoring this clause.
--
Ticket URL: <http://abcl.org/trac/ticket/446>
armedbear <http://abcl.org>
armedbear
#391: "bad place for a wild pathname" on EXT:PROBE-DIRECTORY for NAME containing
#\*
-----------------------------------------------+------------------------
Reporter: mevenson | Owner:
Type: defect | Status: new
Priority: major | Milestone: 1.3.3
Component: interpreter | Version:
Keywords: cl:probe-file ext:probe-directory | Parent Tickets:
-----------------------------------------------+------------------------
John Pallister on #abcl reported problems with configuring ASDF via {{{
(asdf:initialize-source-registry '(:source-registry (:tree (:home
"src/synchromesh")) :inherit-configuration))}}} for which he later traced
down to problems with a pathname NAME containing a #\* character:
{{{
<synchromesh> Ooh, that's interesting - EXTENSIONS:PROBE-DIRECTORY has
found a filename in the specified directory tree that contains a "*".
<synchromesh> Then (much deeper)
org.armedbear.lisp.probe_file$pf_probe_directory.execute(probe_file.java:88)
throws the error.
}}}
The exact error cases here still needs to be determined.
TBD: What does it mean to PROBE-{DIRECTORY,FILE} on a PATHNAME containing
#\*?
--
Ticket URL: <http://abcl.org/trac/ticket/391>
armedbear <http://abcl.org>
armedbear
#443: ENCODE-UNIVERSAL-TIME effectively ignores TIME-ZONE argument
-------------------------+----------------------
Reporter: mevenson | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: interpreter | Version:
Keywords: | Parent Tickets:
-------------------------+----------------------
In <https://mailman.common-lisp.net/pipermail/armedbear-
devel/2017-March/003807.html>
{{{
A contributor to the Maxima project bumped into this while trying
Maxima + ABCL 1.4.0.
CL-USER(1): (ENCODE-UNIVERSAL-TIME 48 1 15 15 8 1995 -23)
3017516508
CL-USER(2): (ENCODE-UNIVERSAL-TIME 48 1 15 15 8 1995 -13)
3017516508
CL-USER(3): (ENCODE-UNIVERSAL-TIME 48 1 15 15 8 1995 13)
3017516508
CL-USER(4): (ENCODE-UNIVERSAL-TIME 48 1 15 15 8 1995 23)
3017516508
CL-USER(5): (ENCODE-UNIVERSAL-TIME 48 1 15 15 8 1995 'foo)
3017516508
Not too surprising, I think -- a glance at
./src/org/armedbear/lisp/time.lisp shows that the TIME-ZONE argument
doesn't take part in the calculations.
TIME-ZONE does come into play in pre-14840 versions of time.lisp and the
results are consistent with other CL implementations, at least for the
examples exercised by the Maxima test suite (date parsing).
}}}
--
Ticket URL: <http://abcl.org/trac/ticket/443>
armedbear <http://abcl.org>
armedbear