* Working out final bugs in theory Theory.
* Getting ready to write his proposal
* Covers a lot of ground
* It presents a unifying theory of things that already conform to it?
* Yes. as well as adding more nice stuff. Still working on a few bugs.
* Also thinking about junctions
* Trying to find a new version of my proposal that makes everybody happy
* That's about it
* Started a use.perl journal
* Posted edited minutes from last week.
* Mostly, reading and musing on larry's posts to 6perl regarding tree transform language
* Simletaniously frightend and other things.
* Agrees with allison - doesn't feel like perl
* may just not feel like the perl i'm used to
* As I see it, the problemspace is different than what you're used to.
* Feels too formal for perl, but it's really quite concise and wonderful
* Relative to haskell?
* No, it's just like haskell, and haskell is good at it.
* This is why i asked allison what she wants to do with trees
* She wants to change it in a small way or transform it to a new tree with a different structure.
* Is this going to change how people work with XML
* The primary goal is for compiler implementaiton, but I think we'd like to make it more general a tool than we've had in the past.
* It doesn't bother the haskell folks, but it feels like we've got too many parens. I sort of wonder if we should branch out into unicode.
* Too many colons, too.
* That's a question I'm going to propose to sixperl.
* The theory proposal covers this somewhat, too. We'll see how it works out.
* We need to figure out what transformations you want to do and then figure out how you want to write them.
P: [ missed a bit here. sorry]
* This week's implementor's meeting was a bit sparsely attended, but we're hoping for more next week.
* [goes on to ramble a bit about P6 project management, what it might possibly mean to "finish" the design for 6.0 and how we can possibly find a sucker who's willing to define how threads will work.]