freenode/lisp - IRC Chatlog
Search
11:27:45
flip214
can't find anything about how to create a new account, though... there's no self-registering, is there?
11:32:50
flip214
Shinmera: thanks, yeah. so no self-registration, I need to bother somebody else. thank you!
11:39:14
_death
if you mean dvi, you can get dpans2 here: http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/doc/standard/ansi/dpans/
11:54:54
KZiemian
I try to start again works on phoe CLUS and I need CL standard precisly for that to know which part of CLHS is not canonical and I can skep it
11:59:35
beach
I don't remember. Sorry. I recall that they were a bit tricky to find. I suppose phoe knows.
13:45:22
Bike
https://github.com/trivial-gray-streams/trivial-gray-streams/blob/master/package.lisp#L51 what's with the dots?
15:09:38
_death
.so files containing linker INPUT directives, and dlopen (and therefore cffi) doesn't support this idiocy
15:12:33
_death
from what I can see, to tell the linker to link with other libraries, though it seems possible to give any linker options
15:26:03
Shinmera
For example, a pie chart of how many systems in quicklisp are written in CL versus other languages. That should prove how dominant of a language it is nowadays.
15:27:56
phoe
One person asked what are the popular libraries on Quicklisp in general because they don't know the modern Lisp ecosystem in general and just want to take a brief look at the most popular libs.
15:28:34
Xach
http://blog.quicklisp.org/2016/03/quicklisp-download-stats-for-february.html -- this might not be the last but it's probably similar
15:34:27
phoe
if the libraries are popular enough, one can google them and end up with their homepages
15:34:52
rpg
In *theory* it should be easy, but not sure how many people put :author in their ASDF defsystem. Goodness knows I usually forget...
15:35:09
Xach
rpg: It's a prerequisite of quicklisp, actually. though many systems are grandfathered in.
15:35:22
Xach
rpg: I've demanded :author, :license, and :description for new projects for several years now.
16:35:03
Fare
Xach: can you upgrade quicklisp's asdf from 2.26 to 3.1.7 ? What are issues with it? 2.26 is really a pain to maintain upgrading from... and upgrade from it means having to reconfigure asdf
16:35:44
Fare
except those that don't, and then I get bad bug requests (e.g. old CLISP release... from 2010)
16:44:53
Fare
In any case, ASDF "best practices" recommend idioms not compatible with ASDF 2 (at least for testing), and lots and lots of systems (including CFFI, IOLib, etc.) require ASDF 3.1 or later.
16:52:33
larsen
Xach: is it possible to tell modules quickloaded directly from those that are loaded to satisfy a dependency? (I reckon it's probably a difficult notion to define precisely)
17:36:59
phoe
Xach: I think it would be enough for your client to fetch dependencies through a different URL that you can then monitor separately
17:37:52
Xach
But, that would require some care, as I can picture other dists using an url structure that can't be harmlessly amended
17:38:54
phoe
And then again, some people might actually depend on (ql:quickload :foo) pulling a lot of dependencies that they'd install anyway, so this way might actually miss some legitimate hits.
17:39:25
phoe
I think a combination of both "installs + dependencies" and these raw downloads could provide better insight, if anything.
17:51:49
flip214
larsen: well, any system not listed in ql-dist:dependency-tree would have to have been loaded manually...
18:20:29
Shinmera
Though nowadays there's also Lack and I don't really know how Lack does even less than Clack does or whatnot.
18:21:37
Shinmera
There's also Radiance, which does as little as Clack, or more than it, depending on what you want :^)
18:29:48
Fare
ACTION wonders what to do with that dozen or so systems in Quicklisp that haven't merged asdf 3.2 fixes after 1-4 months
20:03:50
whoman
wow, ironclad takes as longer to compile and load than everything else ive installed from quicklisp today combined
20:12:31
whoman
Module #<PACKAGE "HOOVY"> requested but while the package exists, it is not a module. [Condition of type MODULARIZE:NOT-A-MODULE]
20:18:05
whoman
define-page was quite the quick example. i am sort of wanting to move ahead and build onto that by using my own packages.
20:20:49
whoman
thanks for your help Shinmera ! sorry for being a newbie, soon i will have my own flow
21:38:24
Xach
http://report.quicklisp.org/2017-07-25/failure-report/lichat-protocol.html#lichat-protocol
21:39:15
Shinmera
The changes to the protocol allowed me to (just now!) implement file sending https://twitter.com/Shinmera/status/889963002048466945
21:40:22
Shinmera
I did a force push with the fixes back when I fixed it, though I'm guessing that doesn't matter, yeah?
23:05:55
pjb
Not really a library, but you can learn. There are a few libraries, like cl-fad to deal with implementation dependent things such as physical pathnames.
23:06:35
pjb
If you want to access specific file systems, you may have to use platform specific API (eg. to access all the POSIX paths on a unix file system).
23:08:52
pjb
Once you have them in memory, it's normal data. There are libraries for parser generators, regexps, etc…
23:15:17
Xach
z3t0: with-open-file is the usual thing to use, then read, read-line, read-char, read-byte, read-sequence
23:16:27
pjb
or the various library accessors: com.informatimago.common-lisp.cesarum.file:…-file-contents