#866: DEPRECATE (after review) some VTABLE functions
--------------------+-------------------------------------------------------
Reporter: bacek | Owner:
Type: RFC | Status: new
Priority: normal | Milestone:
Component: core | Version: 1.3.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
--------------------+-------------------------------------------------------
Comment(by bacek):
Replying to [comment:3 allison]:
> 1. Except that it's impossible to retrieve a bignum value from another
PMC without get_bignum, because an N register can't hold the value.
Ok. Let's add "get_complex". For exactly same reason...
Agree (but dislike it) with math ops.
There is more vtables to review:
* set_bignum_int (which is not used at all.)
* get_repr (which have notice in pdd17 about redundancy with get_string)
* assing_string_native/set_string_native looks pretty duplicates.
* "string" versions of bitwise operators. Do we really need them? How
often they are used. Can we hust replace them with METHODs?
*ADD* more VTABLEs for consistency sake:
* i_logical_or, _and, _xor
--
Bacek
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/866#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
