freenode/#lisp - IRC Chatlog
Search
10:29:07
phoe
beach: I have an unexpected possible collision since one person that I didn't expect to reply to my mail replied sooner than I thought.
12:39:32
phoe
And now I need to figure out whether we want to accomodate both and have a 2.5h+ long meeting or whether we want to split that
12:39:54
phoe
And I'm partial towards the other approach, which means that one of them will happen e.g. a week later
14:37:31
Xach
I don't understand the failure in http://report.quicklisp.org/2020-09-04/failure-report/climacs.html#climacs at all
14:40:47
scymtym
Xach: i ran into that by accident yesterday. i believe this is stale/broken code in climacs which McCLIM now detects
14:41:50
beach
We really should get Second Climacs up and running. *sigh* so much to do, so little time.
14:43:11
scymtym
jackdaniel: i think LISP-STRING used to be defined as a presentation type but was removed at some point. there are two or three other instances
14:51:01
jackdaniel
it defined commands specialized on presentation types, but the symbols were not imported
14:51:17
jackdaniel
so it was trying to define things on symbols which were not designating presentations
14:54:10
_death
apparently (uiop:define-package #:foo (:import-from #:ajhasdjhas/asdjhasdjas)) where the import-from package does not exist, does not signal an error :/
15:03:34
_death
since I use package-inferred-systems it actually should've loaded the appropriate system, but it didn't.. quickloading it worked.. so I'd say something's fishy
15:04:56
_death
it did load another system with a very similar name.. a/b/c/foo loaded and a/b/c/bar was not.. very strange
15:25:11
contrapunctus
Trying to decide on a parser generator library...I've tried esrap, I like the API, but the benchmarks on the MaxPC blog say it's significantly inefficient; MaxPC is AGPL; for some indescribable reason I find smug's API and documentation impenetrable 😔
15:30:13
_death
oh, I screwed up the :import-from.. had (:import-from :package1 :package2) instead of two :import-from clauses
17:48:36
jasom
contrapunctus: if you backtrack alot, esrap will be fast, if you backtrack rarely, it will be slow. I wrote an esrap parser for json and then basically the identical code as a recursive-descent parser and the latter was faster just because there was no backtracking. On the other hand I did a parser for restructured-text tables with a monadic parser and esrap beat the pants off of it, because it
17:52:43
jasom
contrapunctus: aren't smug and MaxPC very similar interfaces? They are both monadic parsers.
18:12:31
contrapunctus
jasom: thanks for telling me about the effect of backtracking on performance; I'll try to analyze how often the language I'm trying to implement requires it, and keep it in mind when choosing a library.
18:13:29
jasom
contrapunctus: I mostly use esrap unless I know parsing will impact performance of the system, fwiw
18:43:32
fiddlerwoaroof
contrapunctus: I wrote a parser for EDN with smug, and it was fast enough but significantly slower than Clojure's implementation (for $work I have to be able to process EDN files that are 10s of MB)
18:44:09
fiddlerwoaroof
The interface isn't horrible, if you know a little about parser-combinators :)
18:46:19
fiddlerwoaroof
ACTION is havign weird issues with emacs allocating and never gcing like 10GB of memory
18:48:18
rig0rmortis
fiddlerwoaroof: have you tweaked gc-cons-threshold? I have (setq gc-cons-threshold 50000000) in my init to gc after 50mb
18:54:32
fiddlerwoaroof
If you need a textual way to serialize data structures, it's one of the better ones :) Fewer limitations than JSON, less annoying than YAML
20:36:09
pve
_death: a follow-up to my metaclass trouble: it seems your suggestion to have one supermetaclass worked, so big thanks