freenode/#lisp - IRC Chatlog
Search
19:03:01
dbotton
Is there a way to execute a command from asdf? So that so when someone does a quicklisp load of my project it runs a git command to git clone a JS component?
19:10:15
_death
dbotton: see https://www.common-lisp.net/project/asdf/asdf.html#The-object-model-of-ASDF
19:11:13
pfdietz
I see some LZW compression algorithms in QL, but is there one by itself intended for general use?
19:11:47
pfdietz
Xach: you wrote on in skippy, but it doesn't appear to be part of the exported interface of that system.
19:12:53
Alfr_
dbotton, could you declare a dependency on that component in the readme instead of trying to retrieve it on every load-system?
19:17:35
Xach
The simplest thing (on a certain axis) is to include all the things you need up front.
19:25:38
Xach
pfdietz: are you interested in a standalone library for lzw for something in particular?
19:32:17
dbotton
So maybe I just describe in demo how if the CDN version fails (or your country can't use) what to do
19:33:17
dbotton
I don't think I want to add into my git tree and don't really want it as a dependency
19:51:16
White_Flame
dbotton: btw, uoip is a part of asdf, so if you're loading via asdf, you shouldn't have to check if it's there
19:53:29
Xach
having uiop does not mean the things you may want to run will be present and run, though.
19:54:24
White_Flame
oh, I thought the implication was testing if uiop was present, might have misread
23:01:40
didi
People, people. Hear me: use `with-standard-io-syntax' when printing sexps to a file and save yourself from the pain.
1:26:15
nij
Reading let over lambda, which refers to assembly code every now and then. Any suggestion on getting started with the minimal amount of assembly, so i can enjoy LOL more? :-) thanks!
1:27:20
pfdietz
Xach: yes, a standalone library for LZW. The use case is compressive similarity of strings.
1:28:23
pfdietz
That is, you can estimate how similar two strings are by knowing how much compressing one helps you compress the other.
3:02:15
Nilby
Is calling your unpublished package something like com.flipper-zapper.floop really the only way avoid future clashes? Or is there a better way?
3:14:12
Nilby
I like package-local-nicknames, but it seems I still have rename every existing package to have those long names.
3:40:31
ldb
Nilby: I think it is supposed that while the package author gives a long name, a nickname should also be given
3:44:32
azrazalea
I know i've done this before but i'm blanking on how. I want to create a macro that defines a new class then stores some extra metadata on the class definition symbol (not on the instance). Essentially extra named documentation. Then later retrieve that metadata elsewhere in my program. It's been too long, can someone point me to the docs I need to review for this? I'm struggling to find it.
3:46:53
Nilby
ldb: Hmmm. I guess one can suggest a package-local-nickname in documentation. But a regular nickname can't clash either.
3:48:17
azrazalea
ldb: Once I have the symbol yes, but classes are in a different symbol namespace right? Sorry if terms are wrong, it has been a couple years
3:49:46
Nilby
azrazalea: You could always look up the extra doc in a hash table of the class name symbols. Otherwise you might have to do something more complicated like subclassing standard-object.
3:58:22
Nilby
I always forget about symbol-plists. It's even easier than the hash table way: (setf (get 'boo :extra-doc) "This is cool.") (get 'boo :extra-doc)
3:58:55
azrazalea
Yeah, that's what I'm aiming for but I'm missing something to get the symbol for the class definition and it's probably something obvious lol