antik issueshttps://gitlab.common-lisp.net/antik/antik/-/issues2021-12-19T11:35:23Zhttps://gitlab.common-lisp.net/antik/antik/-/issues/6readtable problem with clasp2021-12-19T11:35:23ZKarsten Poeckreadtable problem with claspIn clasp we have a problem with the definition of the readtable in
https://gitlab.common-lisp.net/antik/antik/-/blob/master/input-output/readtable.lisp#L24-L27
The `(:macro-char #\# :dispatch)` overwrites all previous definitions for su...In clasp we have a problem with the definition of the readtable in
https://gitlab.common-lisp.net/antik/antik/-/blob/master/input-output/readtable.lisp#L24-L27
The `(:macro-char #\# :dispatch)` overwrites all previous definitions for subchars of `#\#` including `#+`
What is the use of `(:macro-char #\# :dispatch)` anyhow?
From my testing this only works in sbcl, neither in ecl, clasp nor ccl nor clisp.
so please change the line to
```lisp
(named-readtables:defreadtable :antik
(:merge :standard)
#-(or ccl clasp)
(:macro-char #\# :dispatch))
````
or even
```lisp
(named-readtables:defreadtable :antik
(:merge :standard)
#+sbcl
(:macro-char #\# :dispatch))
````https://gitlab.common-lisp.net/antik/antik/-/issues/5Error occurs when using with ECL2020-02-23T22:46:12ZNOEUError occurs when using with ECLhttps://gitlab.com/embeddable-common-lisp/ecl/issues/558
```
(named-readtables:defreadtable :antik
(:merge :standard)
#-ccl
#-ecl
(:macro-char #\# :dispatch))
```
Was fixed at hand, but the following error occurred.
```
Intern...https://gitlab.com/embeddable-common-lisp/ecl/issues/558
```
(named-readtables:defreadtable :antik
(:merge :standard)
#-ccl
#-ecl
(:macro-char #\# :dispatch))
```
Was fixed at hand, but the following error occurred.
```
Internal error:
;;; ** Reader error in file #<input stream "/home/hiro/.local/share/deepspace/quicklisp/dists/quicklisp/software/antik-master-df14cb8c-git/input-output/readtable.lisp" 0x643e8c0>, position 1055:
```https://gitlab.common-lisp.net/antik/antik/-/issues/4grid/iterate.lisp: Compilation error: "Symbol "ROW" not found in the GRID pac...2019-04-30T02:33:58ZKatherine Cox-Budaygrid/iterate.lisp: Compilation error: "Symbol "ROW" not found in the GRID package"I'm working on packaging `antik-base` for [Guix](https://www.gnu.org/software/guix/), and I get variations of this compilation error on all the latest commits. I followed QuickLisp's lead and fell back to e4711a69b3d6bf37b5727af05c3cfd03...I'm working on packaging `antik-base` for [Guix](https://www.gnu.org/software/guix/), and I get variations of this compilation error on all the latest commits. I followed QuickLisp's lead and fell back to e4711a69b3d6bf37b5727af05c3cfd03e8428ba3 which is building.
```
; compiling file "/gnu/store/f6v710009nv1fvk966wfx325ciaal0s4-sbcl-antik-base-0.0.0-1.60c1fae/share/common-lisp/sbcl-source/antik-base/grid/iterate.lisp" (written 30 APR 2019 02:25:26 AM):
; compiling (IN-PACKAGE :ITER);
; caught ERROR:
; READ error during COMPILE-FILE:
;
; Symbol "ROW" not found in the GRID package.
;
; Line: 40, Column: 13, File-Position: 1504
```https://gitlab.common-lisp.net/antik/antik/-/issues/3Reader macros should be installable via a function or named-readtables2020-02-24T02:13:39ZJason MillerReader macros should be installable via a function or named-readtablesGlobally modifying the readtable at system load time may or may not be supported going into the future with ASDF. It's also in general considered poor style for a library.
Instead there should be a function to enable the macro (e.g. (g...Globally modifying the readtable at system load time may or may not be supported going into the future with ASDF. It's also in general considered poor style for a library.
Instead there should be a function to enable the macro (e.g. (grid:enable-reader-macro)), or perhaps the named-readtables library could be used.https://gitlab.common-lisp.net/antik/antik/-/issues/2Cannot export symbol COMMON-LISP:TIME from locked package2017-06-25T09:34:31ZLiam HealyCannot export symbol COMMON-LISP:TIME from locked packagehttp://paste.lisp.org/+3I8W/3http://paste.lisp.org/+3I8W/3Liam HealyLiam Healyhttps://gitlab.common-lisp.net/antik/antik/-/issues/1Should iterate clause definitions be shadowed in antik-user packages?2017-07-12T11:21:11ZLiam HealyShould iterate clause definitions be shadowed in antik-user packages?As of f9265eee569a, antik-user packages (as defined by make-user-package) shadow some iterate symbols, like 'for. This means that to use the ordinary iterate symbols, the package prefix is necessary. Since it is expected that the ordinar...As of f9265eee569a, antik-user packages (as defined by make-user-package) shadow some iterate symbols, like 'for. This means that to use the ordinary iterate symbols, the package prefix is necessary. Since it is expected that the ordinary symbols will be used more frequently than the antik symbols in iterate, perhaps it is better to use the iterate symbols, so that that when antik symbols are needed, the prefix is given.Liam HealyLiam Healy