freenode/#lisp - IRC Chatlog
Search
15:35:54
jeosol
I see a new SBCL is out today. BTW, how are you guys managing and testing with compiler version. I normally just upgrade with a new version and regenerate a bunch of core files.
15:36:39
jeosol
However, I am getting to a point where I may pin things down to use certain version. I have not used roswell, so may be it does what I need. I try not to update on a machine that runs my long jobs
15:41:27
jeosol
Ldb: very good point, I have never had any incompatible issues at all. Only issue is the core files I used, I sometimes run a docker image.
15:42:23
jeosol
yeah, regarding incompatible changes, I occasionally have to deal with "python version hell"
15:46:13
jeosol
ldb: yeah, that's my main issue - though, I could just keep the old versions and use the old binary files. It doesn't take much to generate the core files.
15:47:41
jeosol
I am trying to learn docker .. and its docker-compose, but I haven't been able to make things work well - the part where run a service.
15:47:59
ldb
it might be a good idea to keep the SBCL version util some major upgrades are made to your program
15:59:42
beach
Is it fair to say that the purpose of this function is to take a specialized lambda list and return a generic-function lambda list?
16:02:31
beach
OK. I guess my question is whether things like default values for &optional and &key parameters should be removed.
16:08:58
cl-arthur
the description only says that it removes specializers, though. I'd find it surprising if something described as removing specializers also removes information unrelated to specializers.
16:10:04
jeosol
I took an interest after beach's link. I ran the last command, but didn't get &optional in the rest, but got &rest instead
16:11:38
beach
I'll just write a separate function for extracting a generic-function lambda list from a method lambda list.
16:54:49
hhdave
fiddlerwoaroof: I'm glad you're interested in it. It does use an old parenscript, yes. I tried a newer one but it broke some code I was generating. It would be nice to update it though.
17:09:21
johnjay
hhdave: that reminds me, I was going to ask what are the cutting-edge type libraries in CL
17:09:37
johnjay
I suppose people never remove things from a language. But it can evolve over time with new libraries
17:10:34
phoe
I'd suggest Coalton and Jim Newton's https://github.com/jimka2001/regular-type-expression that are both pretty damn useful
17:18:15
johnjay
i thought it was something weirder or more abtract for specifying context free grammars
18:00:03
loke[m]
Some Climaxima progress: https://peertube.mastodon.host/videos/watch/3113d341-006d-4d35-b4c0-3cebdbdd77ae
19:10:32
exit70[m]
I tried 5.2 (from https://code.google.com/archive/p/mcl/downloads)on 10.4 and 4.2 (from an abandonware site) on 9.1/9.2.2
19:35:47
scymtym
McCLIM is not strictly functional in the sense of, for example, ELM, but it has a concept of presenting data, accepting a user command, then re-presenting the possibly changed data
19:46:40
Josh_2
can I use fast-io to read from a file or do I have to read my data and then I can use fast-io for rapid read writing once in ram?
20:36:16
phoe
so you can create a fast-io buffer from a stream and then use fast-io read functions on that buffer object
21:06:52
phoe
I think that's what happens when sequence reading is not dominated by function call overhead
21:07:58
Josh_2
turns out I've been reading files (when not using alexandria) wrong this entire time
21:12:57
Josh_2
To be fair to fast-io when reading the same file 1000x I reckon my drive will be the bottle neck
23:11:07
jcowan
I'd like to see a use case where a condition type directly inherits from more than one condition supertype. Can anyone think of one?
23:12:57
phoe
for an application named FOO, (define foo-condition () ()) and then (define foo-error (error foo-condition) ()) (define specific-foo-error (foo-error) (...))
23:13:23
phoe
these are the two most obvious ones I can think of, the first one being actually mandated by the CL standard
23:13:47
jcowan
Okay, let me reformulate. Where neither of the direct supertypes are generic ones like simple-condition.
23:14:46
MichaelRaskin
nfs-condition could plausibly be a subtype of both network and filesystem condition
23:14:52
phoe
I guess it's like with classes; whenever you'd otherwise need multiple inheritance for whatever reason..
23:17:22
jcowan
MichaelRaskin: It seems to me that a NFS condition could be either a network or a filesystem condition, but hardly both. If you get a network error, you have no access to the file system, ugye?
23:17:45
phoe
(define-condition person-not-allowed-into-building (person-error building-error) ()) and such
2:07:01
thmprover
Random question: is there any strong consensus about package-name and directory structure? E.g., in Clojure, each namespace has its name be the file name, and subdirectory as prefix to namespace...does Common Lisp informally do likewise? Or is it all pushed in one giant package?
2:10:29
no-defun-allowed
In my implementation of Netfarm, there are 30 files, each about 50-70 LOC, in one package. There are about 80 exported symbols from memory.
2:11:55
PuercoPop
thmprover: There is no strong consensus, but most people use one package per project. There is a one package per file style supported by ASDF and some people do you prefer it. That style is the most similar to the one you'll find in Clojure.
2:13:16
no-defun-allowed
Another interesting example is a CLIM implementation; there are many files with (in-package :clim-internals), but they export symbols in some other packages (CLIM, CLIM-EXTENSIONS, etc). And my networking code and Petalisp have several modules, each with a package.
2:14:09
thmprover
I've just been sweeping my quasi-CAS into a ./math/ subdirectory of my project, it *feels* natural to include ".math." as part of the package name, but that's a Clojure habit I've acquired
2:16:35
no-defun-allowed
The Java teacher at this university told us that you name the files the same name as the classes so that you can always find the implementation of a class without using a search tool. Now, without using a search tool, how do I find the method toUpperCase in java/lang/String.java?
2:24:43
thmprover
One more question: what conventions are there for docstrings? I infer from the few examples given that UPPERCASE is used for function parameters, and when referring to other functions in my own codebase I defined I should wrap the `function-name' in quotes (like thus).
2:26:53
no-defun-allowed
I've always written parameters and function names upcased, or as normal if some noun matches the name of a parameter, eg (defun not-actually-subseq (sequence start end) "Return the contents of a sequence from the start to end positions" ...)