Changes between Version 2 and Version 3 of PackfileTasklist

Show
Ignore:
Timestamp:
12/29/10 19:40:53 (11 years ago)
Author:
cotto
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PackfileTasklist

    v2 v3  
    44 - Don't differentiate between "initial" packfiles and others. We should initialize the interpreter properly, and load all packfiles in through a common interface 
    55 - Break up src/packfile/api.c into a series of smaller files, by separating out functions that work on similar things 
    6  - Allocate Packfile stuctures through the GC fixed size allocator, not mem_sys_alloc and friends 
     6 - Allocate Packfile structures through the GC fixed size allocator, not mem_sys_alloc and friends 
    77 - Don't use PARROT_EXPORT for anything (with *very few* exceptions) in src/packfile/*. This subsystem should be private and should not be used by external utilities 
    88 - Rename subsystem API functions to Parrot_pf_* 
    99 - Don't differentiate between PBC_LOAD and PBC_INIT functions in a packfile 
    1010   - Pending deprecations TT #1895, TT #1896 
    11  - The PackFile structure should keep track of the current PBC_MAIN function, and not rely on storing a reference to it in CURRENT_CONTEXT(interp). This way we can query the main function of any packfile at any time 
     11 - ~~The PackFile structure should keep track of the current PBC_MAIN function, and not rely on storing a reference to it in CURRENT_CONTEXT(interp). This way we can query the main function of any packfile at any time~~ 
    1212 - Packfile functions should not write to Parrot_io_printf or Parrot_io_eprintf directly. Functions should throw exceptions on error, or print errors to an error buffer so an embedding application and choose where to send it. 
    1313 - break compile_or_load file into two functions, one that loads a .pbc file, and one that compiles a PIR function. Deprecate the later. 
     
    2020 
    2121 - All dump-related functions should move to src/packfile/packdump.c 
    22  - These functions should not output to stdout. Either add to a STRING, a StringBuilder, or some kind of new PackfileDumpVisiot 
     22 - These functions should not output to stdout. Either add to a STRING, a StringBuilder, or some kind of new PackfileDumpVisitor 
    2323 - These functions should not be part of struct PackFile_funcs 
    2424 - Actually, do these functions belong in src/packfile/* at all, or in frontends/pbc_dump/*? Or, do they belong as PMC methods?