freenode/#lisp - IRC Chatlog
Search
9:34:47
beach
The 300€ I offered to extract the Cleavir environment code is no longer available. I have almost finished the work myself.
9:38:36
phoe
I know beach and jackdaniel have some, there is the current CCL one for PLNs, and I know stylewarning also has some posted.
9:40:08
beach
Not for what I am proposing. I don't want any old person to apply. Then I would have to deal with explaining to them that they are unqualified, with looking at their existing code, etc, etc.
9:40:46
beach
Oh, and I would like the applicant to have the desire to learn things. Not just make money.
9:56:29
no-defun-allowed
There are libre software funding pages, a lisp presence on some would be interesting.
9:57:02
no-defun-allowed
Also, I have a very small bounty since websocket implementing is not the best use of my time.
9:58:32
no-defun-allowed
Such a client should have methods for reading and writing events, but the client only should pass data events to the user and raise conditions for disconnects.
9:58:34
beach
Posterdati: Maybe you don't know what "bounties" are. They are not employments. Just small amounts of money for specific tasks.
9:59:29
no-defun-allowed
Also, admittedly, I don't know if PayPal will let me use the $3.80 as I don't have a credit card. I think it should, hopefully.
10:01:39
beach
no-defun-allowed: That is a very small amount of money. I doubt you will have any takers.
10:03:31
no-defun-allowed
I do have a rough prototype for a websocket client like I describe, but most of the required features are missing.
10:04:38
beach
Posterdati: In the case of McCLIM, we get regular (monthly?) support from a bunch of contributors.
10:04:41
Posterdati
no-defun-allowed: why don't you read the UNIX Networking Programming manual and Network Programming in ANSI Common Lisp with IOLib?
10:05:21
Posterdati
beach: I see, I'm looking at the site you posted, I'm interested in usign McCLIM
10:05:40
no-defun-allowed
Cause I retch at seeing Unix documentation and streams are much more natural for CL.
10:07:16
Posterdati
no-defun-allowed: I did a client/server using iolib, not easy, but not impossible!
10:07:21
no-defun-allowed
Also, again, the less CFFI, the better. I'm sorry, but it'd give me more shit to maintain and deploy.
10:07:51
no-defun-allowed
CFFI won't work too well on Heroku, and I want to avoid it for everything other than SSL.
10:08:13
Posterdati
no-defun-allowed: since you have to use system libs I do not understand the CFFI problem...
10:09:37
no-defun-allowed
The only C library I want to pull in is SSL, since that's definitely going to be present, everything else is more work.
10:11:04
no-defun-allowed
Additionally, more C means more things that go wrong that I can't gracefully recover from. I'm terrible at prototyping and I've killed a few images from being stupid with CFFI.
10:13:33
no-defun-allowed
Yeah, I have to spawn two threads instead of one to get cl-decentralise talking to it too.
10:14:01
no-defun-allowed
But I suppose the synchronous requirement can be worked with, it's easy to hack on to the other.
10:14:31
no-defun-allowed
There was some kind of fast-io which used static vectors which used CFFI, which I can't disable.
10:16:02
no-defun-allowed
Maybe I need to update the buildpack, since there is an issue with a uiop macro from what I remember.
10:16:24
no-defun-allowed
>i got a very, very weird error using websocket-driver on heroku: https://pastebin.com/4XjhbYQ4
10:18:45
no-defun-allowed
Would that come with sbcl? I think asdf did and they're fairly related libraries.
10:20:25
no-defun-allowed
I don't know, honestly. Heroku does not let you get at a remote repl too easily.
10:21:20
phoe
Though by now I expect it to ship ASDF2 which is ancient as well and many modern libraries refuse to run on it.,
10:26:38
no-defun-allowed
I suppose the SBCL developers have forgotten to add the finewine(tm) program longevity improving libraries.
10:35:23
phoe
So, not SBCL's fault either. Complain to CFFI maintainers that they dropped support for earlier UIOP versions.
12:05:04
dimpase_
their FAQ is rather unclear on it, and in my setup (require :ecl-quicklisp) starts installing things into ~/quicklisp straight away.
12:11:19
dimpase_
one does not want 100 students creating ~/quicklisp and downloading stuff there...
12:13:52
phoe
quicklisp operates with the assumption that users can download arbitrary stuff into the Quicklisp directory
12:15:00
phoe
if you want read-only access to systems, you can run Quicklisp as a privileged user, download the packages from the Internet into a directory that is read-only by other users
12:15:35
phoe
then other users add that directory to their ASDF registry so they can (asdf:load-system :foo) from it.
12:15:56
Inline
like a main base on some dir then everyone with his own clutter of their own quicklisp dir
12:16:52
phoe
you have a system-wide registry (Quicklisp mirror) that is scanned first, and if a system is not found there, then QL/ASDF can search for it
12:18:32
dimpase_
in fact, it's about adding a package into ECL embedded into SageMath... (http://sagemath.org)
12:21:11
Inline
phoe: i.e. installing some libs to arbitrary paths, and keep the pointers in the registry ?
12:24:22
phoe
so: use an external ASDF registry, and Quicklisp on the clients, while making sure that QL is aware of the external registry.
14:32:01
jackdaniel
I've answered this question on the mailing list (about ecl-quicklisp contrib). To sum up: 1. ql should be installed from quicklisp.org (ecl-quicklisp is a conveniance hack), 2. to customize location for ecl-quicklisp contrib do something like: (push '("HOME:QUICKLISP;**;*.*" "/tmp/quicklisp/**/*.*") (logical-pathname-translations "HOME"))
14:33:48
Xach
i get frustrated sometimes when the same question is posted to irc, mailing list, reddit, stack overflow
17:22:00
phoe
What condition type would be the best for the kind of error "START is greater than END"?