#469: [CAGE] revisit t/tools/ops2pm/05-renum_op_map_file.t
---------------------+------------------------------------------------------
Reporter: allison | Owner:
Type: cage | Status: new
Priority: normal | Milestone: 1.1
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by allison):
Your translation of the original Python program is perfect. The original
just made some assumptions about post-1.0 behavior that we never exercised
(since we'd always been pre-1.0).
On your questions:
1. The expectations for ops renumbering for 1.0 and beyond is exactly the
same as pre-1.0. No additional documentation needed.
2. 1.0 isn't a turning point, it's a continuation of business as usual. We
should ditch the code that was designed to handle post-1.0. In fact, I
already ditched the code, so what's needed is to expand the tests to make
sure the behavior pre- and post-1.0 is the same.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/469#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
