Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of luqui (5770)

Wednesday September 21, 2005
11:57 PM

Today's Perl 6 Meeting Notes

[ #26826 ]

Luke

* Working out final bugs in theory Theory.
* Getting ready to write his proposal
* Covers a lot of ground

Jesse

* It presents a unifying theory of things that already conform to it?

Luke

* 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.

Patrick

* 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

Luke

* 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

P:

* Relative to haskell?

L:

* 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.

J:

* Is this going to change how people work with XML

P:

* 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.

L:
* 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]

Jesse:

* 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.]

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • But why are these being put in a blog when they should be put up in a prominant section of the P6/TPF website that has long been very quiet and very low on any real information? I keep hoping that someday someone will get their shit together and instead of focusing on logos and press releases will care about the things that people have been waiting to hear about for years. YEARS.
    • TPF has routinely had people volunteer for this sort of work and drop it. Over and over and over. Then people yell at us because no one wants to do it. They get all upset that the information isn't presented the way they want it, but they won't help. Of course, I understand that not everyone is in a position to help. They have family, or they have some obscure clause in their employment contract or they simply don't want to (which is OK, I understand), and I do want people to keep reminding us of where