Fwd: new lists. perl6-internals-api-*
[email protected] ("David Grove")
| Newsgroups | perl.perl6.meta |
|---|---|
| Message-ID | <[email protected]> |
Sorry for the crosspost (the information was requested). This is where I got the information on the new api groups. I've subscribed to the groups but haven't seen any traffic on them yet. I don't see any reason to believe that this wouldn't be authentic, but if it is, then if I'm not missing some huge discussion somewhere, then somebody's got the cart before the horse... You know anything about this Nat? Nat, this also brings up another issue I hadn't foreseen. If one person (Dan, Sarathy, or whoever, not picking on anybody) leads so many working groups, how can that work into the fairness system that we banged our heads together to eek out? Kudos to Dan for (trying to) take on so much, but the wisdom of this is questionable, even if he can handle all the work. The frustrating part is that I actually want to participate in the parser group. I think I have some to add. The problem is we don't have any language definition from Larry yet, so figuring out a parser seems waaaay premature. We don't even know what's desired in the core, since we're looking toward a minimal core. ============= BEGIN FORWARDED MESSAGE ============= Subscribe by sending mail to [email protected]. For example [email protected] for the first list. More information at http://dev.perl.org/lists CHAIR: Dan Sugalski WORKING GROUP: perl6-internals-api-extensions DEADLINE: Nov 24, 2000 MISSION: Develop the API for perl 6 extensions DESCRIPTION: This group is charged with developing the API perl presents to extensions. This group should develop an RFC for this, as well as a header file, stub source, and as a few rough test programs. CHAIR: Dan Sugalski WORKING GROUP: perl6-internals-api-embed DEADLINE: Nov 24, 2000 MISSION: Develop the API for perl 6 embedders DESCRIPTION: This group is charged with developing the API perl presents to embedding programs. This group should develop an RFC for this, as well as a header file, stub source, and as a few rough test programs. CHAIR: Dan Sugalski WORKING GROUP: perl6-internals-api-parser DEADLINE: Nov 24, 2000 MISSION: Develop the API for the perl 6 parser DESCRIPTION: This group is charged with developing the API for the perl 6 parser/lexer/tokeniser. This group should develop an RFC for this, as well as a header file, stub source, and as a few rough test programs. The parser will be written in perl. CHAIR: Dan Sugalski WORKING GROUP: perl6-internals-syntax-tree DEADLINE: Nov 24, 2000 MISSION: Develop the syntax tree structure for perl 6 DESCRIPTION: This group is charged with developing the structure of the syntax tree (or HIR, if you'd prefer that term) that the perl 6 parser hands off to the bytecode compiler, optimizer, and execution engine. - ask -- ask bjoern hansen - <http://www.netcetera.dk/~ask/> ============== END FORWARDED MESSAGE ==============