phf: i think correct method would really be to get the transaction out as a binary array into shiva, and then have a transaction parser in shiva itself that'll break it down into a sexp or whatever ☟︎☟︎

phf: ben_vulpes: you could hook somewhere like hereabouts http://btcbase.org/patches/makefiles/tree/bitcoin/src/wallet.cpp#L1117 to open a new file and << wtxNew to it

phf: you want to be ready for when "i don't have a smartphone" thing is in full swing in portland. you can be a full blown hipster avantguard

phf: ben_vulpes: here's a phone for you https://www.ebay.com/itm/282003650097

phf: i recently threw out a perfectly working dual-sim nokia something or other, because i thought i lost the battery, but just yesterday i discovered that i had whole two batteries stored elsewhere.

phf: "a face book? i do not poses a face book, i have many regular books though!"

phf: ben_vulpes: t9's not bad, it has an auto-updating dictionary which i only use for names, because it also amuses me to write like i'm from a different planet.

phf: major reason i gave up ios is because getting a working connection proxy requires a full blown vpn going

phf: would make for a lovely torrent dump

phf: one thing i wrote that i was really happy with is a very simple gps coordinates to atlas grid mapper. the thing would basically draw a rectangle with atlas grid number, like p34 A7 and inside the rectangle it'll draw a large red dot which roughly indicates where in the quadrant you are. i was using it extensively on a trip through alaska, because the toy catches gps readily, but naturally can't catch internet connection. so it was a kind of navigation

phf: both times i wrote anything on pythonista was when i was traveling without a computer, and i do it semi-recreationally. with automatic indentation and completion it's not particularly painful, if the goal is to get some interesting computations going, rather then you know "programming environment". it's more of a turtle kind of exercise

phf: pythonista has been around for a while. it's literally the only useful application for the iphone

phf: ben_vulpes: before i finally gave up my ios, i was using pythonista for almost everything, including totp. there's some python totp implementation that i lifted from somewhere, that can be easily ported. i gave up writing a barcode recognizer, though it's not a particularly daunting task with numpy

phf: i think a proper cuntoo doesn't even need x11, bash scripts, lynx and framebuffer to render images if need be

phf: i mean guy says so himself "Specifically, you never really get absolute proof. There’s always some innocent or coincidental explanation that could sort of fit the evidence — maybe it was all a stupid mistake."

phf: even though i hear that sbcl now has a evaluator added back?

phf: there's two sbcl apologists further in thread, one of them saying "I don't mind provocative /per se/, but what you were saying gives the a| impression that SBCL is willfully bad, as opposed to in development. But lumping it in with willfully noncompliant systems for this reason, | given it's version number, is inappropriate." and the other one is a core dev saying that they might add it. of course the expected behavior is still not there

phf: there's not a single article on the subject of compilation, but here's the complete thread https://www.xach.com/naggum/articles/search?q=recompile+reeval&sort=of specific test that he proposes is in https://www.xach.com/naggum/articles/3243682048034314@naggum.no.html and the "dun work" reaction https://www.xach.com/naggum/articles/3243737082731156@naggum.no.html

phf: from location A to location B to location C where they are expected)

phf: fwiw bulk of these tools have been written through the 90s and what was worthwhile from orcland was published that way then. until silent takeover by latex & 1.8gb tex installations happened and none of these tricks work anymore (because the necessary hooks are so deep within the layer of cruft it's near impossible to get to them, and one way they did it is through standard file system lay out, that requires a chain of compilation stages to move files

phf: source reading can be a preprocessor stage (which is a lot saner to do in common lisp than elsewhere), this is also how traditional tex handles orclangs, before xetex and luatex and such. special ascii sequences to represent local lang glyphs and if you don't want to write those by hand, you use (or write) a tool that takes a local encoded document and translates it into ascii

phf: naggum has a rant about it specifically

phf: trinque: ccl used to do it that way actually, interested parties might want to poach that code. they call the concept Rune and it's basically a way to support orcograms in a 8bit lisp

phf: that's a very broad statement

phf: obviously a typo

phf: you're not going to even approach a performance of a compiled sbcl. at best you would do is non-jited lua

phf: and vops in turn were an equivalent of a lisp machine microcode

phf: cmucl fwiw was designed like a lisp machine (though it had damage done to it by modernizers already), where the evaluator + vops was you primary interaction mode, and compilation was a way to evaluate a piece of code to a vop like status

phf: none of these are properties of sbcl past certain vintage though though, sbcl is already a modernization of common lisp

phf: i think naggum has a rant about the last one

phf: asciilifeform: you know after staring at a lot of bad c code and last two days worth of conversations, i don't think there's much wrong with sbcl, but then i haven't looked at sbcl code in about a year at this point. i think i was mostly objecting to overall trajectory of lisp ecosystem

phf: looking at their commit history there's a lot of "utf8 support in ..." and "nls ..." which is probably the proverbial fleas bringing dog

phf: source development in the slightest. He's putting out a windows-only

phf: tcc. But it's still stagnant, because Fabrice put a Windows developer