#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 jkeenan):

 Replying to [ticket:469 allison]:
 > Just before the release, rurban pointed out that
 tools/dev/opsrenumber.pl had a feature to completely change its
 functionality when the major version changes to "1". The problem being
 that this functionality is entirely unused so far, poorly tested, and not
 actually what we want. I changed it in r37525 so it has no special
 behavior for different version numbers.
 >
 > 4 tests in t/tools/ops2pm/05-renum_op_map_file.t fail as a result, so
 I'm marking them as TODO. These tests need to be updated to reflect our
 expectations for op renumbering in 1.0 and beyond.

 ''tools/dev/opsrenumber.pl'' started out its life as a Python program.
 Coke filed [http://rt.perl.org/rt3/Ticket/Display.html?id=53976 RT 53976]
 nearly a 1 year ago to have it rewritten in Perl 5, which I did .  Said
 rewrite is what is being tested in
 ''t/tools/ops2pm/05-renum_op_map_file.t''.  But I reached the limits of my
 understanding of the issues involved and, IIRC, Coke didn't consider that
 ticket closable.  So it was assigned to Nobody.

 Here is a far-from-exhaustive list of questions that arise at this time:

 1.  Where do we document what 'our expectations for ops renumbering for
 1.0 and beyond' currently are?

 2.  If 1.0 should still be considered the major turning point, is it safe
 to ditch the code that was designed to handle pre-1.0?

 Thank you very much.[[BR]]
 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/469#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to