gabriel_laddel: kk. I should be discussing this in design documents anyways.

gabriel_laddel: t) rather than just a false positive. Again, I've never written C, and perhaps the ast is so complicated that it's actually impossible to get any useful information out of it, but my current experience suggests that having this ability is a good idea. Building something like `slime-who-calls' suddenly becomes simple.

gabriel_laddel: Why might one want to see the C ast? Let's say that we've got a codebase like the linux kernel, or opengl drivers. You know that somewhere you've got some stuff that talks to the hardware, but grep returns false positives. You instead pull the ast into memory, query across it for the bits your looking for. False positives now indicate something about the language (i.e., that I don't understand it as well as I though

gabriel_laddel: As for PGP, I'm assuming that I'm going to have to spend a decent amount of time with the codebase and reading the spec. Perhaps not.

gabriel_laddel: trinque: in any case, I hate everything about the browser.

gabriel_laddel: "As for what language I'll be using on any given project, it will be determined entirely by what is correct for the project."

gabriel_laddel: mircea_popescu: I have some code now that converts javascript to parenscript

gabriel_laddel: asciilifeform: I'm assuming, at least for now, that I'm going to have to /look/ at the current PGP sources (thus the C sexprast ). This has no bearing on what will be released other than - I will do what makes sense given the situation.

gabriel_laddel: asciilifeform: Sorry, I was being less than clear - this is only for development.

gabriel_laddel: As for what language I'll be using on any given project, it will be determined entirely by what is correct for the project. If I hack something out in CL, but switch it over to C, I'll do that. If it makes sense to release a protopye that is hacked together C+CL+CFFI I'll do that. In any case, both of these come after getting the #b-a distro finished.

gabriel_laddel: My current plan for dealing with these projects: The haskell package Language.C.AST parses C99 entirely, taking into account all GCC extensions. I'm going to pay someone to add a sexpr backend to it so I can work it into my CL toolchain.

gabriel_laddel: asciilifeform: gossipd requires C. PGP, CL (at least, this is where I'd start).

gabriel_laddel: asciilifeform: thank you, this is what I wanted.

gabriel_laddel: asciilifeform: you had a alternate name for gossipd based on russian theater that had some relation to the nazis. I couldn't find the wiki article again, care to point me to it?

gabriel_laddel: asciilifeform: I'v M-x rembered (or something) the previous thread on the matter for when I return to it.

gabriel_laddel: mircea_popescu: as for now, I just want to have a clear idea of what the interface is, what the problems are etc.

gabriel_laddel: " As far as I can tell, were one to extrapolate from the given information to a set of concrete requirements we see that NixOS plans to rewrite the build scripts for every version of every project on unix. Again, this is insane. The correct thing to do in this situation is to realize the utter impossibility of the task that has been set forth and re-evaluate one's approach.[1]" << [1] links to the quote previously d

gabriel_laddel: wtf is this, we're discussing a footnote in something I posted.

gabriel_laddel: (I don't parse that)

gabriel_laddel: That said, I've had the experience several times of reading trilema or the logs, not immediately grokking it, returning a day later to have it all 'click'. I'm thinking that might happen here.

gabriel_laddel: Hmm.. This is what I was attempting to communicate.

gabriel_laddel: hoever it was, and I'm fairly sure I grok ASCII's plan and will be handling some intro documentation for it + figuring out how the PGP code needs to interface with it exactly.

gabriel_laddel: as for my id, I'm currently fixing <irritant to livelihood>. First chance I get I'm sitting down and sorting out the whole GPG thing. As it stands I was not particularly happy with the documentation it supplied and wasn't sure which parts I'd have to rewrite. My previous key got destroyed in a failed backup becuase I didn't spend enough time on it the first time around. Also, I don't think gossipd is happening via w

gabriel_laddel: well, when someone is tweaking the design of something and it produces extremely complex and counter-intuitive behavior I point them to that quote.

gabriel_laddel: I've had that exact experience with programming.

gabriel_laddel: as for the fight in our realm, I'd like to buy 10ks of AMD opterons K8 chips and reverse engineer them. Give designs to China.

gabriel_laddel: what I would like to see is an actual fight.

gabriel_laddel: ^ Correct. I ended up using it because I needed to quickly build a linux distro and someone told me it could do some things it couldn't really do.

gabriel_laddel: Thanks for the feedback. I'll keep that in mind.

gabriel_laddel: The last message from me in that thread contains a brief discussion of the "why" of lisp, that is, what separates it from being 'just another language'. Figured I'd post it in here because your previous trilema post discussing reverse polish notation and Erik Naggum + many #b-a messages didn't communicate to me that lisp has 'clicked' yet for many people.

gabriel_laddel: then don't bother reading I suppose.