dynoplibs in core or no?
julian.notfound at gmail.com
Wed Jun 2 19:51:34 UTC 2010
> Just some clarification, is this issue the same as what is described in
> http://trac.parrot.org/parrot/ticket/1663 ?
I think is the same.
>> I think that the best way to solve that particular problem is to kill
>> the open and close opcodes.
> Do you mean kill them as in remove the open/close opcode from Parrot,
> or to just not allow people to use the opcodes from PL/Parrot? I am in
> favor of either. It seems odd to have open and FileHandle.open do
> exactly the same thing.
Remove from Parrot. They are redundant with the FileHandle methods,
provide no advantage and add a lot of complexity.
More information about the parrot-dev