#1885: Parrot_load_bytecode should only load bytecode
-------------------------+--------------------------------------------------
Reporter: whiteknight | Owner: cotto
Type: RFC | Status: new
Priority: normal | Milestone:
Component: core | Version: master
Severity: medium | Keywords: pir, pbc
Lang: | Patch:
Platform: all |
-------------------------+--------------------------------------------------
The function src/packfile.c:Parrot_load_bytecode() is too magical. It not
only loads bytecode, but it also does some rudimentary extension string
matching to also allow it to load .pir and .pasm file. This is extremely
magical and is not made clear through the function's name.
This function is exposed primarily through the load_bytecode PIR op, which
has similar magical behavior.
I suggest that we eliminate the magical behavior of this function and the
opcode that exposes it: load_bytecode and Parrot_load_bytecode should
*only* load bytecode files under any extension. If the user wants to
compile a PIR source file they should use the PIR compreg.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1885>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
