21:10:51ebrascasabrac: How to document my lisp code. eg: https://github.com/ebrasca/turtle-graphics
21:20:34sabrac<ebrasca>Are you asking for mechanics within the code, how to automatically write an api or thoughts on content?
21:21:10sabracYour forward and jump functions are both documeted, so you could use a library like staple to generate documentation from the document strings .
21:21:24sabracBut if I look at (forward) and (jump), both functions are documented, but they are not clear.
21:22:05ebrascasabrac: for me forward and jump are clear.
21:22:06sabracThe documentation for (forward) says ""Move turtle n units forward and draw"
21:22:30sabracBut the documentation for jump says ""Move turtle n units forward"
21:22:57sabracI am wondering about the function names compared to the what they apparently do
21:24:17ebrascasabrac: forward extrude , and jump only move
21:25:53sabracBTW, staple's website is at https://github.com/Shinmera/staple. I found it easy to use.
22:46:52blackwolfanyone have a suggestion or recommendation for filling a large array of '(unsigned-byte 8) with random bytes?
22:48:10blackwolfwant something more efficient than calling (random 256) severral million times.
22:49:35Bicyclidineyou'd rather call (random 65536) and shift a few million times?
22:52:37Bicyclidinei think sbcl gets 32-bit words from mersenne, so you could get those and shift them in
22:58:01blackwolfwas thinking something along the lines of that, e.g. (random (expt 2 64)) ... would prefer something like memcpy rather than shift, maybe a solution involving ldb. that would require getting access to an integer as a block of bytes. perhaps cffi.
23:00:40shrdlu68blackwolf: Why not read /dev/urandom?