freenode/#sbcl - IRC Chatlog
Search
2:29:19
ckonstanski
SB-EXT:RUN-PROGRAM is susceptible to file descriptor exhaustion. https://paste.pound-python.org/show/WMDcPZuhAjQY7s0J9ft6/
3:10:54
corci
Project sbcl-master-windows » Windows_7_32bit build #2098: FAILURE in 35 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2098/
4:06:26
corci
Project sbcl-master-windows » Windows_7_32bit build #2099: FIXED in 41 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2099/
12:00:42
scymtym
stassats: re highlighting in source text: maybe https://github.com/scymtym/text.source-location/tree/future has something useful
12:16:26
stassats
i could instrument each standard reader macro, and that wouldn't be much of a problem, but i'd also prefer it to work on non-standard macros
12:22:40
stassats
i could change the path format that sbcl uses, but then it wouldn't work on older slimes and it would be hard to use on s-exp forms, not text
12:22:53
scymtym
stassats: reader macros in general or reader macros performing recursive calls to READ?
12:23:51
stassats
scymtym: in general, i'm wrapping each form returned by READ in a structure, so things like #+, which examine what read returns, do not work
12:26:10
stassats
i could build a parallel structure, just by recording the bounds and then establishing nesting, etc.
12:27:04
scymtym
that sounds similar to what eclector does: https://github.com/robert-strandh/Eclector/blob/master/code/concrete-syntax-tree/read-cst.lisp
12:28:26
stassats
i guess #-abc returns zero values, so i need to stop building including the collected substructures until read returns non-zero values