New dreamscape: hilly city, brick buildings; a huge square bar, too well lit, where I hang out. There's a 20ish finely dressed blond with gauze completely covering her face and neck, named Amanda, who hangs out here too, but not with me; I only know her name because everyone else here seems to know it, and they call out greetings.
My mesquite beer has an odd smell and taste to it; quite bitter, for sure won't need any hops; and there's some kind of solvent smell to it, not alcohol either. Anyway, I bottled it a few days ago. It only filled two and a half bottles. We'll see if it's any better after aging.
The store was out of apple juice Saturday, so I bought grape juice instead. To my surprise, the vinegar-making scum didn't form on it. Perhaps if I alternate cider with wine, I'll have fewer problems reusing the same jars.
Still eating grocery-store meats. Can't bring myself to hunt. Hope this is just a phase.
I wish I knew more about Python internals. Trying to make it a stack-based language for a more maintainable development method. What I have in mind is having every non-None result, that isn't assigned or otherwise used, go onto a data stack, made persistent across programs through an envvar PYTHON_DATA_STACK. Items are taken from the stack using '_', similar to how the interactive commandline works (though that stack is only one element deep, and unavailable within programs). The new binary should still work fine for most "normal" Python programs. There is, though, the possibility of stack overflows if there are lots of ignored values. Might need a new keyword 'discard' to take care of those.
Back to blog or home page
last updated 2009-07-22 21:22:10. served from tektonic