Changes between Version 14 and Version 15 of GSoc2011

Show
Ignore:
Timestamp:
03/11/11 16:41:25 (11 years ago)
Author:
whiteknight
Comment:

+details about a few projects

Legend:

Unmodified
Added
Removed
Modified

  • GSoc2011

    v14 v15  
    3030== Project Ideas == #projects-up-for-grabs 
    3131 
    32 Put ideas for GSoC 2011 Projects here. Try to follow the existing format. 
     32Put ideas for GSoC 2011 Projects here. Try to follow the existing format. Here's a template that you can copy+paste to insert a new idea: 
     33 
     34=== <New Project Idea (Copy this template)> === 
     35 
     36 * '''Difficulty''': <UNKNOWN> 
     37 * '''Links of Interest''': <NONE, please add some> 
     38 * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
     39 * '''Details''': <NONE, add details inline, or link to a page that has them> 
     40 * '''Expected Deliverables''': <UNKNOWN, Please list what the deliverables will be> 
    3341 
    3442=== Embed Parrot into Inkscape === 
    3543 
    36  * '''Difficulty''': <UNKNOWN> 
     44 * '''Difficulty''': <UNKNOWN (x/5)> 
    3745 * '''Links of Interest''': http://inkscape.org/ 
    3846 * '''Possible Mentors''': <UNKNOWN> 
    … …  
    4250=== Bytecode Emitters for POST === 
    4351 
    44  * '''Difficulty''': <UNKNOWN> 
     52 * '''Difficulty''': 4/5 
    4553 * '''Links of Interest''': <NONE, please add some> 
    4654 * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
    47  * '''Details''': <NONE, add details inline, or link to a page that has them> 
    48  * '''Expected Deliverables''': <UNKNOWN, Please list what the deliverables will be> 
     55 * '''Details''': Several languages compile down to an abstract syntax tree type called POST. POST is the last stage of analysis and transformation before output code generation. Update existing POST, or create a new POST library capable of outputting bytecode directly. You should not output PIR and rely on the PIR compiler to generate the bytecode. Emphasis for this project is placed on the ability to output working bytecode, not necessarily on the quality of the generated bytecode nor the throughput performance of the converters. 
     56 * '''Expected Deliverables''': A POST extension or POST replacement which is able to generate bytecode. Includes necessary unit tests and all necessary documentation. 
    4957 
    5058=== TapTinder === 
    … …  
    5866=== LALR Parser Generator === 
    5967 
    60  * '''Difficulty''': <UNKNOWN> 
     68 * '''Difficulty''': 5/5 
    6169 * '''Links of Interest''': <NONE, please add some> 
    6270 * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
    63  * '''Details''': <NONE, add details inline, or link to a page that has them> 
    64  * '''Expected Deliverables''': <UNKNOWN, Please list what the deliverables will be> 
     71 * '''Details''': Create an LALR parser generator tool. The tool should be written in one of the lower-level languages which run on Parrot (PIR, NQP, Winxed, other) for maximum portability. The parser generator should take a language specification and compile it into an LALR parser in a manner similar to YACC/Bison. The generator parser likewise can be in any suitable language. For this project, a working LALR parser generator engine is more important than the ability to understand a huge number of input patterns and pattern modifiers. 
     72 * '''Expected Deliverables''': A working LALR parser generator capable of converting a language specification into an LALR parser. Necessary unit tests, examples, and documentation must be included. 
    6573 
    6674=== Language Interop === 
    … …  
    8290=== New Parrot Debugger === 
    8391 
    84  * '''Difficulty''': <UNKNOWN> 
     92 * '''Difficulty''': 4/5 
    8593 * '''Links of Interest''': <NONE, please add some> 
    8694 * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
    87  * '''Details''': Expand on parrot-instrument, build awesome tools on top of it, get it fully working again. 
    88  * '''Expected Deliverables''': <UNKNOWN, Please list what the deliverables will be> 
     95 * '''Details''': Parrot needs a new debugger. There exists a toolset called "parrot-instrument" which can be used to insert introspection, analysis, and manipulation functions into Parrot internals. You may optionally (preferrably) use Parrot-Instrument as the basis for your new debugger or create a new one from scratch. A successful debugger will have the ability to set break-points on subroutines at the PIR and HLL level, set watchpoints on registers or individual PMCs, and introspect state information from a running program. The debugger should read information from annotations so that it can be used to work with various HLLs. Performance of code executing under the debugger is not a primary concern for the initial deliverable. 
     96 * '''Expected Deliverables''': A working debugger with the capabilities listed above. In addition, the successfull student should provide adequate unit tests, code examples, and documentation. 
    8997 
    9098=== Subroutine-Level Profiler === 
    … …  
    112120 * '''Expected Deliverables''': <UNKNOWN, Please list what the deliverables will be> 
    113121 
    114 === <New Project Idea (Copy this template)> === 
    115122 
    116  * '''Difficulty''': <UNKNOWN> 
    117  * '''Links of Interest''': <NONE, please add some> 
    118  * '''Possible Mentors''': <UNKNOWN, please volunteer!> 
    119  * '''Details''': <NONE, add details inline, or link to a page that has them> 
    120  * '''Expected Deliverables''': <UNKNOWN, Please list what the deliverables will be> 
    121