Howdy, The state of how we keep track of deprecations is changing. I have made a branch called leto/deprecations_as_data
You can see a diff of it from master here: https://github.com/parrot/parrot/compare/master...leto%2Fdeprecations_as_data It adds some very basic scripts that give examples of what kind of stuff we can do with deprecations as data. They output stuff like this: https://trac.parrot.org/parrot/ticket/843 Action methods in rules https://trac.parrot.org/parrot/ticket/1778 2.10 charset, charsetname, find_charset, trans_charset https://trac.parrot.org/parrot/ticket/1554 2.4 ManagedStruct reallocations based on shape changes https://trac.parrot.org/parrot/ticket/1103 2.1 implicit optional named parameters https://trac.parrot.org/parrot/ticket/463 1.1 PCT::HLLCompiler from Perl 5's Test::Harness https://trac.parrot.org/parrot/ticket/1406 2.1 get_results opcode order and features https://trac.parrot.org/parrot/ticket/1561 2.4 Auto-vivification of nested aggregates https://trac.parrot.org/parrot/ticket/508 1.5 JSON and Config;JSON https://trac.parrot.org/parrot/ticket/868 1.5 PAST::Val node generation Note that it is immediately obvious here that we don't have an eligible version for "Action methods in rules". Should we? I renamed DEPRECATED.yaml to docs/changes/api.yaml, since the old name was too specific, since experimental stuff is listed in there as well. I don't really care what we call the file, I just care that we have the data in this file available, soon. I would like to get feedback from others on whether they would like to merge this to master. I would like to do this soon, because the deprecation-killling-bacek-robot is on the loose and I already will have some merge conflicts to deal with. Duke -- Jonathan "Duke" Leto [email protected] http://leto.net _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
