freenode/#sbcl - IRC Chatlog
Search
19:01:19
scymtym
that could be a reasonable compromise. although i would worry about users piling all the code into DEFMACRO forms to get better source tracking
19:02:20
stassats
which means i need to finish my current level of support and just it and note where it falls short
19:04:20
scymtym
i suspect, the unwrap-and-reconstruct approach with the single-occurrence heuristic for atoms will work fairly well in practice
19:04:42
corci
Project sbcl-master » without-unicode,ubuntu_trusty_32bit build #3124: FIXED in 21 min: http://ci.cor-lab.de/job/sbcl-master/featureset=without-unicode,label=ubuntu_trusty_32bit/3124/
19:04:59
corci
Project sbcl-master » default,ubuntu_trusty_32bit build #3124: FIXED in 21 min: http://ci.cor-lab.de/job/sbcl-master/featureset=default,label=ubuntu_trusty_32bit/3124/
19:06:03
stassats
scymtym: for multiple use, could track depth first order of atoms, or something, but i'm afraid some reader macros might change the output orde
19:07:04
stassats
but each list form would be handled separately, so chances that a single list has multiple duplicate atoms are smaller
19:10:01
scymtym
maybe one of those surveys across all code in quicklisp would be in order to determine how frequent the different cases occur
19:12:34
stassats
if source location handling could be standardized, and things like named-readtables are used, it could prove functionality to supply routines to handle custom macros
19:13:30
stassats
so that you don't have to send definitions to slime and can extend it independently
19:13:36
scymtym
ACTION waits for a scheme person to join and be like "you know about syntax objects, right?"
19:15:25
corci
Project sbcl-master-windows » Windows_7_32bit build #2108: FIXED in 30 min: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_32bit/2108/
19:15:26
scymtym
same goes for WITH-CURRENT-SOURCE-FORM, imo, since macros have no other way of indicating which part of the input caused a particular problem
19:17:42
scymtym
if you go the racket/guile route and have macro writers manipulate syntax objects, the situation is different
19:21:04
corci
Project sbcl-master » fancy,ubuntu_trusty_32bit build #3124: FIXED in 37 min: http://ci.cor-lab.de/job/sbcl-master/featureset=fancy,label=ubuntu_trusty_32bit/3124/
19:21:36
scymtym
user programmable source locations would also be nice. for custom defFOO macros. i think lispworks already has something like that
19:25:25
scymtym
ok, i have one question though: do we have a smaller hammer than (coerce … 'function), i.e. that doesn't compile lambda expression, but higher level than SB-KERNEL:%COERCE-CALLABLE-TO-FUN?
19:25:26
corci
Project sbcl-master » safepoints,ubuntu_trusty_32bit build #3124: FIXED in 41 min: http://ci.cor-lab.de/job/sbcl-master/featureset=safepoints,label=ubuntu_trusty_32bit/3124/
19:28:21
scymtym
i can use that. i thought we might have something else since it looks pretty internal
19:35:02
scymtym
dougk_: COERCE-TO-INTERPRETED-FUNCTION turns lambda expression into interpreted functions. i want to only accept functions and function names
19:35:20
corci
Project sbcl-master » fasteval,ubuntu_trusty_32bit build #3124: FIXED in 51 min: http://ci.cor-lab.de/job/sbcl-master/featureset=fasteval,label=ubuntu_trusty_32bit/3124/
19:44:15
corci
Project sbcl-master » ccl,ubuntu_trusty_32bit build #3124: FIXED in 1 hr 0 min: http://ci.cor-lab.de/job/sbcl-master/featureset=ccl,label=ubuntu_trusty_32bit/3124/
20:57:53
stassats
read-preserving-whitespace is exactly like read when the recursive-p argument to read-preserving-whitespace is true.
21:46:52
dougk_
stassats: that aspect may be broken but the other aspect is whether it is permissible to for read-char to hit EOF ever. if recursive-p it can't, so I think that much works
23:35:19
stassats`
well, read-preserving-whitespace with recursive-p behaving exactly like read, that means read will be passed recursive-p as T as well, so it means read will be preserving whitespaces?
23:35:41
specbot
The RECURSIVE-P argument: http://www.lispworks.com/reference/HyperSpec/Body/23_acb.htm
23:36:22
stassats`
shouldn't they have said that read with recursive-p behaves like read-preserving-whitespace?
23:39:47
stassats`
sbcl returns the same result for the second example, but a different for the first, ccl is reversed
23:40:38
stassats`
"However, if read had been used instead of read-preserving-whitespace", but read-preserving-whitespace is using recursive-p, so it's exactly the same
1:40:13
corci
Project sbcl-master » fancy,MAC_OS_mavericks_64bit build #3128: FIXED in 30 min: http://ci.cor-lab.de/job/sbcl-master/featureset=fancy,label=MAC_OS_mavericks_64bit/3128/
6:58:36
corci
Project sbcl-master-windows » Windows_7_64bit build #2113: FAILURE in 3 min 24 sec: http://ci.cor-lab.de/job/sbcl-master-windows/label=Windows_7_64bit/2113/