libera/#commonlisp - IRC Chatlog
Search
1:53:57
pillton
I have a function which signals MODULE-ERROR when invoked as (F :error). I'd like F to perform a different action and emit a warning when invoked as (F :warn-and-reuse). Unfortunately, CL:WARN only signals conditions of type WARNING. Would you create a new condition class MODULE-WARNING or write a version of WARN which accepts ERROR conditions?
1:54:44
Bike
i would not try to signal an error as a warning, because that confuses how callers can respond to it
1:54:55
Bike
e.g. muffle-warning is an appropriate restart for a handler to use for a warning but not an error
1:56:51
pillton
Yeah. My thoughts as well. The downside of MODULE-ERROR is it tends to be a subclass of a lot of operation specific errors. Reproducing the hierarchy for the warning would be pain.
3:18:34
jmes
I'm wondering how to use apply/funcall/mapcar/etc. on macros - well obviously I can't but what should I do when I want to pass macros around like functions?
3:23:29
beach
The point of the macro AND is to avoid evaluating some forms when a preceding form turns out to be NIL. If you already have a list of values, there is no point in the macro AND, so you would use a function instead.
3:35:03
White_Flame
but that's what the macroexpansion does, for the given number of arguments, make a NIL-testing tree with early exit. The lambda will contain that expansion for 2 parameters
3:35:47
White_Flame
and really, "turns the AND into a function" is more "wraps the AND in a function"
11:08:08
lisp123
First hit on Google was https://rdrr.io/cran/qdapDictionaries/man/GradyAugmented.html
11:48:46
hayley
lisp123: What I did around this time last year, as we used it for university work, was to run Minecraft with shaders on. That way the GPU would warm your computer room up.
11:49:38
hayley
In a pinch, model checking or fuzz testing can work, though in my experience CPUs make for worse heaters.
11:50:35
lisp123
i wonder if you could do some cryptomining for the same and make some $$ on the side
11:52:30
hayley
They also tend to be tuned in a way that makes interactive use of the computer unbearable, too. So best stick with the classics, if you want to use the computer.
13:10:53
jackdaniel
zgaduj zgadula: should `#+ (or) (badum +tss+ #<compute-me>)` in a file cause reader to signal an error?
13:12:31
Bike
i don't think it's possible in general to figure out where a #<whatever> ends, since the whatever could have arbitrary text
13:14:05
Bike
in clasp we used to have a test that did something like #+(or) #gblablabla, #g being an undefined reader macro. but there's obviously no way to handle that well, since the #g could introduce arbitrary syntax and the reader can't tell when the expression reads
13:14:47
Guest74
::notify lisp123 I think I'm going to make a github with all the Moby files as I had to dig them out of archive.org. They're also at project gutenberg but they rather stupidly present the readme's as the text so you have to dig and get the links to an ftp site.
13:23:16
Guest74
I'm starting to think this Ward guy might have been a hoarder. I'm not sure I see the general purpose of a word list with entries such as AAAA AAAS AAPSS. Nor do I understand why he basically chose a different format for every list.
13:25:41
Guest74
I'm starting to think composable dictionaries of specific points of view would be better. Any thoughts? Do i really want to check for spelling mistakes against acronyms if I'm not using any acronyms?
13:28:20
Bike
trying to spell check acronyms seems like a fool's errand since anyone can introduce a new one
13:28:53
Guest74
I wish there was an easy way to see how much space an object was taking up. writing out the combined dictionaries in a structured format came out to ~100megs, about 3/4 of that was white space from pretty printer.
13:31:56
beach
Guest74: You can probably find a pretty good approximation. But I suspect there is nothing to worry about. In memory, you can probably also do a lot of sharing.
13:32:37
beach
Guest74: Like the trie data structure can save a lot of space, and there are a bunch of fairly common encoding schemes that will make it even more compact.
13:37:31
Guest74
I still see a use in pov dictionaries for definitions. the word salt in context of cook, chemist, geologist is different.
13:39:15
Guest74
I'm going to load things into tries today and see how much difference it makes. At least one of the trie libraries out there has huge dependencies, so maybe it might be better to stick with hashtables if there's not much difference.
13:46:26
Guest74
TIL there are 9 different ascii encodings of IPA + arpabet and dictionary writers use them all, not to mention the proprietary phonetic encodings of companies. I've got a translater going now so I'm thinking of storing pronounciations in IPA with some sort of marker for language/dialect. Or wrap it in a struct with encoding type, dialect etc...
13:46:27
Guest74
and then you can choose to translate to your preferred encoding (cause most of them look like gobbledygook)