#469: [CAGE] revisit t/tools/ops2pm/05-renum_op_map_file.t
---------------------+------------------------------------------------------
Reporter: allison | Owner: jkeenan
Type: cage | Status: assigned
Priority: normal | Milestone:
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Changes (by allison):
* milestone: 1.2 =>
Comment:
Jim,
It's not supposed to add new opcodes to ops.num. Those have to be manually
added, and that's an intentional control step, so someone has to think
about which ops are being added. But, new ops must always be added to the
end of the file (unless you want to manually renumber all the ops that
follow your insertion point, which would be insane). What opsrenumber.pl
does is put them in a sane order. (For example, if you added a new form of
the 'print' opcode that takes an extra argument, for long-term
maintainability we don't really want it to numbered 1295, while all the
other 'print' opcodes are numbered 300-315.)
I'm also removing the 1.2 milestone from this ticket, as it's not a target
for any particular release.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/469#comment:10>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
