libera/#commonlisp - IRC Chatlog
Search
14:07:13
pve
Hi, intrigued by White_Flame's "dot" macro suggestion, I tried implementing a version of it. I think it turned out alright, although I'm still unsure if it could be used to create truly readable code. Maybe in certain situations..
14:10:55
beach
Using operations is a much better idea that names of slots. But of course, I need to be careful with what I say, or else it will be branded as "oop nonsense".
14:11:30
pve
There's one thing I'm wondering: should the default placement of the "current input value" to the chain of operations be first, or last. I.e. (+ _ 1 2 3) or (+ 1 2 3 _)
14:13:56
pve
many functions have keyword or rest parameters, which could mean that "first" is a better default
14:14:00
hayley
I think "arrow" libraries have multiple macros, one macro for either case, and one which allows using a (rather unhygenic) name like <> to specify where the value should go.
14:17:58
hayley
As an aside I'm not a big fan of access-esque accessors, since you can write accidentally quadratic code when provided with lists rather than vectors, or perhaps alists rather than hash tables here.
14:21:41
hayley
Anyways; underscore-predicate might be better written with AND rather than WHEN, and I like to use a pattern matching library for parsing list structure.
14:28:41
pjb
pve: http://groups.google.com/group/comp.lang.lisp/msg/1bab4b5bae1fdca3 http://groups.google.com/group/comp.lang.lisp/msg/190d771c0e033a1c
14:32:14
White_Flame
really I consider such path traversal operations to be most appopriate for regulard datastructures, not general objects
14:32:49
hayley
beach: A fun word to use is "anti-modular". (Reading logs - what is a "class" if not an "OOP class"?)
14:34:03
beach
hayley: Honestly, I did not read what cedb had to say after those initial "nonsense" comments.