freenode/lisp - IRC Chatlog
Search
17:08:19
rumbler31
is there a way with usocket to see if there are more bytes available to be read on a datagram socket without blocking?
17:16:36
phoe
Lisp test framework question. Is there anything in Lisp that allows me to do stuff like http://paste.lisp.org/display/351234 ?
17:16:43
phoe
Basically - declare what a test case should do in terms of test steps, then define its implementation while marking the individual test steps, then use that information when displaying error information?
17:39:39
Shinmera
I don't particularly see the point in separating the description of what happens and its implementation, though?
17:41:40
phoe
Shinmera: I see such a point though. I want to export my test cases as HTML, and for this, I need a textual representation for them.
17:42:12
Shinmera
Still no need to separate, though. You can also mix the description and extract it.
17:50:01
phoe
I mean - no problem, this is doable using the same reader macros that I have in my example. Just stuff the test step description in the same place where the evaluated expression will be.
17:52:25
rumbler31
according to the docs, not specifiying a timeout blocks, specifiying a timeout will cause the call to return no later than the timeout, or a timeout of 0 should return immediately if no input is available.
17:58:26
rumbler31
wait-for-input with timeout is returning immedately, but is returning the socket I gave it, not nil
18:01:41
phoe
rumbler31: returning the socket you gave it? are you sure you checked that "fresh list" thing that WAIT-FOR-INPUT has?
18:02:23
rumbler31
I'm going senile. I just didn't focus while I was reading the description of the function. I see how to elicit the behavior I expect now
18:27:23
rumbler31
is there a shortcut or config item for the slime inspector to default the slot view to "un-alphabetically
18:27:46
nosefouratyou
I am getting this error dexador.error:http-request-forbidden and I don't understand what the period means between dexador and error.
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.