#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: |
--------------------+-------------------------------------------------------
The opcodes that are remaining in src/ops/experimental.ops are all marked
as deprecated (based on a conversation on IRC with allison).
My thought regarding those opcodes was that even though experimental.ops
has been marked as subject to removal, that we should give these the
benefit of the doubt and officially announce them as deprecated in 1.0 and
then kill them.
Allison suggested (I think) that we simply remove them, since we've said
all along they are experimental.
Now that I've moved all the non-deprecated ops into their more permanent
homes, I figured I'd ask feedback on the remaining ops... Rip them out now
or post 1.0 ?
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/415>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
