#pest | 2023-03-27

hehe http://zzz.st/up/5F0Osbq0/

07:36

thoguht my asembler was bugy

~ 2 hours 47 minutes ~

10:23

http://logs.bitdash.io/pest/2023-03-24#1025217 << and as soon as i said that btcbase decided to crash

10:23

Logged on 2023-03-24 11:22:39 phf[4]: and then things simply stopped working en mass, hosting providers closed, new hosting providers encourage s3 style "spin up instance per task", etc. probably btcbase is the most long running casual process i have at this point

10:25

http://logs.bitdash.io/pest/2023-03-27#1025272 << http://logs.bitdash.io/pest/2022-12-05#1017412 and many others

10:25

Logged on 2023-03-27 07:36:02 jonsykkel: hehe http://zzz.st/up/5F0Osbq0/

10:25

Logged on 2022-12-05 11:22:11 phf[awt]: i maybe wasn't articulate on the point, but i still think that sexps make for a poor interchange format (and neither bolix nor cadr used them for that)

10:27

but if you're going to use them as serialization format, from common lisp, then you'd better know exactly what you're doing

10:30

the documentation for write http://www.lispworks.com/documentation/HyperSpec/Body/f_wr_pr.htm#write has a bunch of `printer control variables` which affect the print in a variety of ways. they can be passed to some functions explicitly (write/write-to-string), and some functions bind them implicitly for convenience

10:34

specifically variables of interest are *print-escape*/*print-readably*, or :escape and :readably as arguments, they decide between "intended to look good for people" and "intended to be acceptable to read"

10:35

so patching above to (... (write-to-string x :escape t :readably t) ...) will produce desired result

~ 18 minutes ~

10:54

􏿽but with that out of the way for this particular sequence sbcl has a funny bug, because of course it does. with just :escape t it prints `#\Space` as `#\ `, and it just happens that it breaks the line on #\ being the last element. so when you read it back instead of it being `#\ `

10:54

􏿽it's actually `#\<Newline>` and you get back #\newline instead of #\space

10:59

the printer facility is so elaborate, you can do (write '(defun ...) :escape t :readable t :pretty t) and it'll give you a pretty-printed source code back, which knows how to indent elaborate things like loop macro

11:00

e.g. http://paste.deedbot.org/?id=NQ8u

~ 1 hours 11 minutes ~

12:11

http://logs.bitdash.io/pest/2023-03-27#1025280 << 5 difrent print functions and none of them do the useful thing of binding all those control vars by default

12:11

Logged on 2023-03-27 10:30:14 phf[4]: the documentation for write http://www.lispworks.com/documentation/HyperSpec/Body/f_wr_pr.htm#write has a bunch of `printer control variables` which affect the print in a variety of ways. they can be passed to some functions explicitly (write/write-to-string), and some functions bind them implicitly for convenience

12:11

with-standard-io-syntax does at least

12:16

http://logs.bitdash.io/pest/2023-03-27#1025285 << should wire that into editor to auto format stuff

12:16

Logged on 2023-03-27 10:59:08 phf[4]: the printer facility is so elaborate, you can do (write '(defun ...) :escape t :readable t :pretty t) and it'll give you a pretty-printed source code back, which knows how to indent elaborate things like loop macro

~ 1 hours 13 minutes ~

13:29

asciilifeform

jonsykkel: what were you trying to do ? ( ... write x86 asmer in cl ? )

13:34

asciilifeform: im writing secd machine in c first 2 get a feel for it and wanted to test it quickly without having any reader

13:34

asciilifeform

a

13:35