Changes between Version 2 and Version 3 of PackfileTasklist
- 12/29/10 19:40:53 (3 years ago)
v2 v3 4 4 - Don't differentiate between "initial" packfiles and others. We should initialize the interpreter properly, and load all packfiles in through a common interface 5 5 - Break up src/packfile/api.c into a series of smaller files, by separating out functions that work on similar things 6 - Allocate Packfile st uctures through the GC fixed size allocator, not mem_sys_alloc and friends 6 - Allocate Packfile stuctures through the GC fixed size allocator, not mem_sys_alloc and friends 7 7 - 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 8 8 - Rename subsystem API functions to Parrot_pf_* 9 9 - Don't differentiate between PBC_LOAD and PBC_INIT functions in a packfile 10 10 - 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 - 12 12 - 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. 13 13 - break compile_or_load file into two functions, one that loads a .pbc file, and one that compiles a PIR function. Deprecate the later. … … 20 20 21 21 - 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 PackfileDumpVisi ot 22 - These functions should not output to stdout. Either add to a STRING, a StringBuilder, or some kind of new PackfileDumpVisi 23 23 - These functions should not be part of struct PackFile_funcs 24 24 - Actually, do these functions belong in src/packfile/* at all, or in frontends/pbc_dump/*? Or, do they belong as PMC methods?