Ticket #598 (new roadmap)
bytecode migration tool
| Reported by: | allison | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.1 |
| Component: | none | Version: | |
| Severity: | medium | Keywords: | |
| Cc: | Language: | ||
| Patch status: | Platform: |
Description
Write a tool to translate one bytecode format to another.
Extra advantage if the changes to make can be specified in a simple syntax, and if the translations can be chained. (That is, once you write a file that details the changes from 2.0 bytecode to 2.6 bytecode and another one with the details of 2.6 bytecode to 3.0 bytecode, the translation tool is smart enough to use the two files to translate 2.0 bytecode to 3.0 bytecode by translating it to 2.6 as an intermediate step.)
The tool will also have to give warnings about opcodes and PMCs that no longer exist, as these can't be mechanically translated. Tell the user to regenerate the bytecode from source instead.
Change History
Note: See
TracTickets for help on using
tickets.
