#415: experimental ops safe to remove?
--------------------+-------------------------------------------------------
Reporter: coke | Owner:
Type: RFC | Status: new
Priority: normal | Milestone: 1.0
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
--------------------+-------------------------------------------------------
Comment(by coke):
A few notes:
- Experimental ops aren't numbered.
- let's not delete the file; it can be typically empty, but an easy place
to add things during dev releases; we can make sure it's empty before the
stable releases, forcing us to either adopt or reject proposed opcodes.
- I've already saved off most of the used ones.
- there are only 8 opcodes left in experimental.ops; hardly a huge gap,
even if they WERE numbered.
- removing them immediately after 1.0 gives us 4 months to test before the
next stable release.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/415#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
