Spent all day doing yard shit. Probably more tomorrow. Ugh. Least I’ll probably get a chance to go fishing Wednesday or Thursday.
Camera’s not too shabby.
So here’s some eggrolls I made. Postbot wins. Back to work now, sigh.
Postbot. Seems ok.
And all the apps I give a shit about are free in the android market. Including one for WordPress =). Really digging andirc, connectbot, andftp, compass, and a few others in particular. Sometimes have to fight with the soft keyboards spelling correction but its usually dead on. All in all I’m happy as a baby in a topless bar.
From the site:
“laridae, family: gulls and terns
laridae, dot-net: netlabel for encoded highs and lows
[la-ri-dä] is a netlabel, that means we distribute music via the internet. and we do this for free. why? because it’s the best and easiest way to make YOU listen to it.
we try to provide a wide range of styles, everything from idm/indietronics to rock/industrial, defining ourselves as a kind of counterpart to the other 95% of netlabels, which are providing hardly anything but minimal dub-house stuff.”
“The Lemon program is an LALR(1) parser generator. [...] Both the source code to lemon itself and the code that lemon generates are in the public domain. [...] Lemon is maintained as part of the SQLite project. “
Why to give a shit in a nutshell, from the docs:
* In yacc and bison, the parser calls the tokenizer. In Lemon, the tokenizer calls the parser.
* Lemon uses no global variables. Yacc and bison use global variables to pass information between the tokenizer and parser.
* Lemon allows multiple parsers to be running simultaneously. Yacc and bison do not.
Switch “type” for “class” and “function” for “generic method” and it’s pretty much half of CLOS with some nice GC and CSP flavored concurrency written in a C-ish syntax.
More interestingly it looks like using the channels as continuations it’d be really easy to translate CPS code to, and I could definitely see something like termite being built atop it.
All in all it seems pretty fucking cool so far.
Since I’m not fighting with C anymore, I’m back to plagiari… I mean ‘researching’, ideas. And while reading Thinking About Lots of Things at Once without Getting Confused: Parallelism in Act 1 I came upon this bit in the context of futures and actors:
Call COMBINE-RESULTS-OF-SUBGOALS on the result of
Creating a FUTURE to solve INDEPENDANT-SUBGOAL-1, and
A FUTURE trying to solve INDEPENDANT-SUBGOAL-2.
It may not be the first such construct, but it’s at least older than I am.