freenode/lisp - IRC Chatlog
Search
19:04:34
nosefouratyou
I have stuff like "0: #<CL-OANDA::INSTRUMENT #x30200235235D>" when inspecting; is it possible to change the value of #x30200235235D to something readable? or is that a specific number generated to address it?
19:06:44
Bike
nosefouratyou: it's an "identity". it's only intended to help a human reader, so it's okay to change. you can control how objects are printed by defining a method on print-object.
19:11:03
Bike
it would be something like (defmethod print-object ((object instrument) stream) (print-unreadable-object (object stream) (format stream "blah")))
20:22:44
pjb
phoe: stakeholders NEVER write tests cases, even in English. This has been demonstrated by man.centuries of cucumber test writting done exclusively 100.000000000000% of the time by PROGRAMMERS.
20:23:04
pjb
So the question is why do you want to bother with English? Just write lisp! We're lisp lovers!
22:37:59
quotation
pjb: I'm entirely for deprecating the entirety of the english language if not wholly extending it further into a "special" dialect accompanying the flavors of homoiconicity
22:50:00
slark
when i pass a variable to the macro it fails, but it works with a number can't really understand why it works
22:51:08
slark
Bike: well i know the macro def should be (list 'setq var (list '- var amount))) but well was just trying to mess a bit
22:51:48
Bike
and it sets var (not the symbol passed to the macro, var, every time) to (+ var amount)
22:58:48
pjb
Since this variable has not been declared (in the compilation environment) the actual behavior is actually implementation dependent.
23:00:15
slark
well in fact was thinking why should i return an expression to inc a variable when the inc could be done at expansion time
23:01:09
pjb
Because expansion time is normally done at compilation time, long before the values of the arguments are known.