log4cl question:<DEBUG> [07:45:28] weblocks/request-handler request-handler.lisp (handle-request app)
When I right click on a package in slime's repl (in emacs, for example on weblocks/request-handler as shown above)
I get this error
log4slime-popup-menu: Wrong type argument: listp, #[257 "ÁÀ9\0ÂÀÃNÄ\"\0ÅÀK!\0À\"" [log4slime-popup-menu x-popup-menu plist-get menu-prop :filter identity] 6 nil "@e"]
Has anyone encountered this error before?
@nonsameer_twitter I found such post https://club.dns-shop.ru/digest/29666-materinskie-platyi-s-otechestvennyimi-protsessorami-elbrus-1s-i-el/ about these processors. The price is quite expensive – article says the it will cost about 120'000 rubles ($1600) for processor and motherboard. But I didn't find these in our online market stores.
Why do you want to by these processors?
Especially from the ones who used it for real. I just dabbled with it.
Cheers
[package 40ants-doc/external-index]...............
[package 40ants-doc/commondoc/reference].
;
; caught ERROR:
; READ error during COMPILE-FILE:
;
; Package UIOP/CL does not exist.
;
; Line: 246, Column: 38, File-Position: 11840
;
; Stream: #<SB-INT:FORM-TRACKING-STREAM for "file /home/josh/quicklisp/dists/ultralisp/software/temp-AA0HXSVW-20210907183410/src/builder.lisp" {100A700293}>
; Debugger entered on #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {100AA82EF3}>@k1d77a:scyldings.com what Lisp implentation and ASDF are you using? On SBCL 2.1.2 and ASDF 3.3.4.13 I have no any problems with UIOP/CL package.
Anyway, I've fixed this issue and new version will be built on Ultralisp in a few minutes. Update your distribution version.
(asdf:asdf-version) output.
1 reply
11 replies
:synchronized t under SBCL, and the version with the lock was faster. Probably there is no need to make code more complex. Especially if some other implementation has something like :syncronized and somebody might support them to making Lack's code even more complicated.
Many implementations have their own standard extensions which might be useful.
When you are writing an end-user application you might choose to agree to the vendor lock and use these extensions.
When you are writing a library for other programmers it is better to make it compatible with standard as much as possible. To accomplish this, you have three options:
- don't use implementation extensions;
- use them with conditional compilation – this makes your code uglier and harder to maintain;
- use compatibility layers to encapsulate implementation details.
By the way, when you choose to use bordeaux-threads, you already use a compatibility layer. There are more such libraries. Most of them are collected at the site: http://portability.cl/
I found some hash table wrappers here https://sabracrolleton.github.io/short-descriptions and at https://quickdocs.org/-/search?q=hash, but none of them support synchronized tables.