IRC channel logs
2026-06-30.log
back to list of logs
<old>so I wonder something <old>do we want #vu8 to interpret bytes in it in base 16 instead of 10 <old>rn we need to do: #vu8(#xC #xA #xF #xE) <old>would it be nice to just do: #vu8(C A F E) <old>also, wondered that bytevector should be printed in base 16 instead of 10 <old>tho that's a printing preference I suppose <lloda>it would require a different prefix i think <lloda>it's p unfortunate having u8 and vu8 mean the same thing but it doesn't look fixable <JohnCowan>in Chibi the bytes are printed as #xnn, excrpt for 0 <rlb>old: if bytestrings had allowed an arbitrary number of hex digits before the semicolon, and depending on your needs, that might be an alternative #u8"\x098b15134a101e35437ffaa9de5bcde76f5fe8c7;" but iirc the spec only allows one or two hex digits before the semicolon. <rlb>or #u8x"098b15134a101e35437ffaa9de5bcde76f5fe8c7"? We could also consider just extending our bytestrings to allow arbitrary runs of hex digits. That'd of course affect the parser, and cause us to not notice malformed "proper" bytestrings. I assume the goal here is "more compact bytestrings" (or more natural when what you have is hex)? <janneke>trying to do their bit upholding the lisp curse, /me writes their first poor-mans define-method/type-dispatching macro <janneke>re: wip-peg-enhancements branch, dispatching on PEG tree-ish "objects" <janneke>this should hopefully help a lot in moving dezyne off of goops <jan0t>also more importantly, I saw the d-bus implementation in scheme, I know guile is scheme but I am new in those things <jan0t>guile can import modules written to "scheme" <mwette>there is guile g-golf (packaged in debian, ubuntu) <jan0t>every scheme code i can import within guile? <jan0t>the reference manual tells what kind of codes are considered compatible? <ekaitz>jan0t: guile is more or less compatible with R5RS, R7RS and probably with some R6RS <daviid>sneek: later tell jan0t g-golf is also in netbsd and homebrew