The packfile structure is indeed considered unstable. We have some changes and improvements planned to the file format in the coming months. The exact file format is really considered to be an internal implementation detail. What we will be trying to do soon is to provide a stable API for building and reading packfiles through libparrot. Once available, this API will remain stable, even if the underlying file format is not.
IMCC is really the only reliable way to make complete packfiles right now. It will stay available for the foreseeable future, so there's no rush to get away from it yet. --Andrew Whitworth On Sat, Feb 5, 2011 at 10:17 AM, Patrick R. Michaud <[email protected]> wrote: > TT #451 says that the packfile structure is 'experimental'. > Does that mean that the packfile format is unstable -- i.e., > it doesn't follow the deprecation policy? > > More to the point, if a compiler is writing its own packfiles > instead of using imcc to do it, is the code that generates the > packfile guaranteed to work across supported releases? > > Or does IMCC remain Parrot's only supported interface for generating > bytecode? > > Pm > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
